TEST-INFRA: [ci-pipeline-design] Run nox sessions in parallel within CI jobs #3418

Open
opened 2026-04-05 16:37:43 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: chore/ci-nox-parallel-within-jobs
  • Commit Message: chore(ci): run nox sessions in parallel within lint and security jobs
  • Milestone: (none — backlog)
  • Parent Epic: #3204

Description

In the .forgejo/workflows/ci.yml file, the lint and security jobs run multiple nox sessions sequentially.

  • The lint job runs nox -s lint and then nox -s format -- --check.
  • The security job runs nox -s security_scan and then nox -s dead_code.

These nox sessions are independent and can be run in parallel to speed up the execution of these jobs.

Subtasks

  • Modify the ci.yml file to run the nox sessions in the lint and security jobs in parallel.
  • Ensure that the logs from the parallel nox sessions are still captured correctly.
  • Verify that the jobs continue to function as expected after the change.

Definition of Done

  • The nox sessions in the lint and security jobs are run in parallel.
  • The execution time of the lint and security jobs is reduced.
  • The CI pipeline remains stable and reliable.
  • 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 details.
  • 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 v3.8.0. 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-nox-parallel-within-jobs` - **Commit Message**: `chore(ci): run nox sessions in parallel within lint and security jobs` - **Milestone**: *(none — backlog)* - **Parent Epic**: #3204 ## Description In the `.forgejo/workflows/ci.yml` file, the `lint` and `security` jobs run multiple `nox` sessions sequentially. - The `lint` job runs `nox -s lint` and then `nox -s format -- --check`. - The `security` job runs `nox -s security_scan` and then `nox -s dead_code`. These `nox` sessions are independent and can be run in parallel to speed up the execution of these jobs. ## Subtasks - [ ] Modify the `ci.yml` file to run the `nox` sessions in the `lint` and `security` jobs in parallel. - [ ] Ensure that the logs from the parallel `nox` sessions are still captured correctly. - [ ] Verify that the jobs continue to function as expected after the change. ## Definition of Done - [ ] The `nox` sessions in the `lint` and `security` jobs are run in parallel. - [ ] The execution time of the `lint` and `security` jobs is reduced. - [ ] The CI pipeline remains stable and reliable. - [ ] 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 details. - [ ] 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 v3.8.0. 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
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.

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