TEST-INFRA: [ci-pipeline-design] Consolidate redundant setup steps in ci.yml #3389

Open
opened 2026-04-05 16:22:32 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: chore/ci-consolidate-redundant-setup-steps
  • Commit Message: chore(ci): consolidate redundant setup steps into reusable composite action
  • Milestone: (none — backlog)
  • Parent Epic: (see orphan note below)

Description

The .forgejo/workflows/ci.yml file contains a significant amount of redundant setup steps across multiple jobs (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, helm). Each of these jobs repeats the following steps:

  • Install Node.js
  • actions/checkout@v4
  • Install uv and nox
  • Cache uv packages

This duplication makes the workflow file unnecessarily long and difficult to maintain. Consolidating these steps into a reusable composite action or reusable workflow will reduce the maintenance burden and make future changes to the setup process easier to apply consistently.

Subtasks

  • Investigate using a reusable workflow or a composite action to consolidate the common setup steps across all CI jobs
  • Refactor the ci.yml file to use the new reusable workflow or composite action
  • Ensure that all CI jobs (lint, typecheck, security, quality, unit_tests, integration_tests, e2e_tests, coverage, build, helm) continue to function as expected after the refactoring
  • Run nox (all default sessions) and verify no regressions
  • Verify coverage >= 97% via nox -e coverage_report

Definition of Done

  • The redundant setup steps in ci.yml have been consolidated into a single, reusable component (composite action or reusable workflow)
  • The ci.yml file is shorter and easier to maintain
  • All CI checks pass successfully after the changes have been merged
  • A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation
  • The commit is pushed to the remote on the branch matching the Branch in Metadata exactly
  • The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone Test Infrastructure. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `chore/ci-consolidate-redundant-setup-steps` - **Commit Message**: `chore(ci): consolidate redundant setup steps into reusable composite action` - **Milestone**: *(none — backlog)* - **Parent Epic**: *(see orphan note below)* ## Description The `.forgejo/workflows/ci.yml` file contains a significant amount of redundant setup steps across multiple jobs (`lint`, `typecheck`, `security`, `quality`, `unit_tests`, `integration_tests`, `e2e_tests`, `coverage`, `build`, `helm`). Each of these jobs repeats the following steps: - Install Node.js - `actions/checkout@v4` - Install `uv` and `nox` - Cache `uv` packages This duplication makes the workflow file unnecessarily long and difficult to maintain. Consolidating these steps into a reusable composite action or reusable workflow will reduce the maintenance burden and make future changes to the setup process easier to apply consistently. ## Subtasks - [ ] Investigate using a reusable workflow or a composite action to consolidate the common setup steps across all CI jobs - [ ] Refactor the `ci.yml` file to use the new reusable workflow or composite action - [ ] Ensure that all CI jobs (`lint`, `typecheck`, `security`, `quality`, `unit_tests`, `integration_tests`, `e2e_tests`, `coverage`, `build`, `helm`) continue to function as expected after the refactoring - [ ] Run `nox` (all default sessions) and verify no regressions - [ ] Verify coverage >= 97% via `nox -e coverage_report` ## Definition of Done - [ ] The redundant setup steps in `ci.yml` have been consolidated into a single, reusable component (composite action or reusable workflow) - [ ] The `ci.yml` file is shorter and easier to maintain - [ ] All CI checks pass successfully after the changes have been merged - [ ] A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation - [ ] The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly - [ ] The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone Test Infrastructure. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

⚠️ Orphan Issue — Manual Linking Required

This issue was created without a known parent Epic. Per CONTRIBUTING.md, orphan issues are not permitted — every issue must be linked to a parent Epic using Forgejo's dependency system (this issue blocks the parent Epic).

Action required: A project maintainer must:

  1. Identify the appropriate parent Epic for CI pipeline / test infrastructure improvements
  2. Create the dependency link so that this issue blocks the parent Epic

The focus area is ci-pipeline-design under the Test Infrastructure supervisor workstream.


Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

⚠️ **Orphan Issue — Manual Linking Required** This issue was created without a known parent Epic. Per CONTRIBUTING.md, orphan issues are not permitted — every issue must be linked to a parent Epic using Forgejo's dependency system (this issue **blocks** the parent Epic). **Action required:** A project maintainer must: 1. Identify the appropriate parent Epic for CI pipeline / test infrastructure improvements 2. Create the dependency link so that this issue **blocks** the parent Epic The focus area is `ci-pipeline-design` under the Test Infrastructure supervisor workstream. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.7.0 milestone 2026-04-05 17:19:34 +00:00
freemo removed this from the v3.7.0 milestone 2026-04-06 23:52:22 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core#3389
No description provided.