TEST-INFRA: [ci-pipeline-design] Run independent nox sessions in parallel #1679

Open
opened 2026-04-02 23:28:39 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: task/ci-parallel-nox-sessions
  • Commit Message: ci(pipeline): run independent nox sessions in parallel to reduce CI execution time
  • Milestone: v3.8.0
  • Parent Epic: #376

Background and Context

The default nox sessions are currently run sequentially in the CI pipeline. Many of these sessions are fully independent of one another and could be executed in parallel to significantly reduce the overall CI execution time.

For example, lint, format, typecheck, security_scan, dead_code, complexity, and adr_compliance are all static analysis / quality-gate sessions with no inter-dependencies. The test sessions (unit_tests, integration_tests) could also be run in parallel with the static analysis checks.

Subtasks

  • Audit all nox sessions and classify each as independent or dependent (i.e., must run after another session)
  • Identify which sessions can safely run in parallel without race conditions or shared state conflicts
  • Restructure the CI workflow (e.g., ci.yml) to run independent sessions as parallel jobs
  • Ensure test sessions (unit_tests, integration_tests) are parallelised with static analysis checks where safe
  • Verify the CI pipeline remains stable and all sessions still pass after restructuring
  • Measure and document the reduction in overall CI execution time

Definition of Done

  • Independent nox sessions (lint, format, typecheck, security_scan, dead_code, complexity, adr_compliance, etc.) are run in parallel in the CI pipeline
  • Test sessions (unit_tests, integration_tests) are parallelised with static analysis checks where safe
  • The CI pipeline is stable and reliable — no regressions introduced
  • The overall CI execution time is measurably reduced
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `task/ci-parallel-nox-sessions` - **Commit Message**: `ci(pipeline): run independent nox sessions in parallel to reduce CI execution time` - **Milestone**: v3.8.0 - **Parent Epic**: #376 ## Background and Context The default `nox` sessions are currently run sequentially in the CI pipeline. Many of these sessions are fully independent of one another and could be executed in parallel to significantly reduce the overall CI execution time. For example, `lint`, `format`, `typecheck`, `security_scan`, `dead_code`, `complexity`, and `adr_compliance` are all static analysis / quality-gate sessions with no inter-dependencies. The test sessions (`unit_tests`, `integration_tests`) could also be run in parallel with the static analysis checks. ## Subtasks - [ ] Audit all nox sessions and classify each as independent or dependent (i.e., must run after another session) - [ ] Identify which sessions can safely run in parallel without race conditions or shared state conflicts - [ ] Restructure the CI workflow (e.g., `ci.yml`) to run independent sessions as parallel jobs - [ ] Ensure test sessions (`unit_tests`, `integration_tests`) are parallelised with static analysis checks where safe - [ ] Verify the CI pipeline remains stable and all sessions still pass after restructuring - [ ] Measure and document the reduction in overall CI execution time ## Definition of Done - [ ] Independent nox sessions (`lint`, `format`, `typecheck`, `security_scan`, `dead_code`, `complexity`, `adr_compliance`, etc.) are run in parallel in the CI pipeline - [ ] Test sessions (`unit_tests`, `integration_tests`) are parallelised with static analysis checks where safe - [ ] The CI pipeline is stable and reliable — no regressions introduced - [ ] The overall CI execution time is measurably reduced - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator
freemo added this to the v3.8.0 milestone 2026-04-02 23:29:40 +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.

Blocks
Reference
cleveragents/cleveragents-core#1679
No description provided.