TEST-INFRA: [ci-pipeline-design] Use matrix strategy for parallel Python version testing #1712

Closed
opened 2026-04-02 23:33:11 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: task/ci-matrix-parallel-python-version-testing
  • Commit Message: chore(ci): use matrix strategy for parallel Python version testing
  • Milestone: v3.8.0
  • Parent Epic: #1678

Background and Context

The current CI pipeline runs tests on all supported Python versions sequentially. This is inefficient and increases overall CI build time. Using a matrix strategy in the CI workflow will allow tests to run in parallel across different Python versions, significantly reducing the overall CI build time.

Expected Behavior

The CI workflow should use a matrix strategy to run tests in parallel for all supported Python versions, reducing the overall CI build time.

Acceptance Criteria

  • The CI workflow uses a matrix strategy to run tests in parallel for all supported Python versions.
  • The overall CI build time is reduced as a result of the parallel execution.

Subtasks

  • Modify the CI workflow (.forgejo/workflows/ci.yml) to use a matrix strategy for Python versions.
  • Ensure the matrix is driven by the SUPPORTED_PYTHONS list defined in noxfile.py.
  • Update job names to include the Python version (e.g., unit_tests (3.13)).
  • Verify that the tests are running in parallel across Python versions.
  • Measure and document the impact on CI build time.
  • Update features/ci_workflow_validation.feature to assert the matrix strategy is present.
  • Run nox (all default sessions), fix any errors.
  • Verify coverage >= 97% via nox -s coverage_report.

Definition of Done

  • All subtasks above are completed and checked off.
  • The CI workflow is updated to use a matrix strategy for parallel Python version testing.
  • The CI build time is measurably reduced.
  • 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%.

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

## Metadata - **Branch**: `task/ci-matrix-parallel-python-version-testing` - **Commit Message**: `chore(ci): use matrix strategy for parallel Python version testing` - **Milestone**: v3.8.0 - **Parent Epic**: #1678 ## Background and Context The current CI pipeline runs tests on all supported Python versions sequentially. This is inefficient and increases overall CI build time. Using a matrix strategy in the CI workflow will allow tests to run in parallel across different Python versions, significantly reducing the overall CI build time. ## Expected Behavior The CI workflow should use a matrix strategy to run tests in parallel for all supported Python versions, reducing the overall CI build time. ## Acceptance Criteria - The CI workflow uses a matrix strategy to run tests in parallel for all supported Python versions. - The overall CI build time is reduced as a result of the parallel execution. ## Subtasks - [ ] Modify the CI workflow (`.forgejo/workflows/ci.yml`) to use a matrix strategy for Python versions. - [ ] Ensure the matrix is driven by the `SUPPORTED_PYTHONS` list defined in `noxfile.py`. - [ ] Update job names to include the Python version (e.g., `unit_tests (3.13)`). - [ ] Verify that the tests are running in parallel across Python versions. - [ ] Measure and document the impact on CI build time. - [ ] Update `features/ci_workflow_validation.feature` to assert the matrix strategy is present. - [ ] Run `nox` (all default sessions), fix any errors. - [ ] Verify coverage >= 97% via `nox -s coverage_report`. ## Definition of Done - [ ] All subtasks above are completed and checked off. - [ ] The CI workflow is updated to use a matrix strategy for parallel Python version testing. - [ ] The CI build time is measurably reduced. - [ ] 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%. --- **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:35:16 +00:00
Author
Owner

Closing as duplicate of #1539 (matrix strategy for Python versions).


Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Closing as duplicate of #1539 (matrix strategy for Python versions). --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo 2026-04-02 23:41:41 +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.

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