TEST-INFRA: [ci-pipeline-design] Implement dependency caching in CI #1639

New issue

Closed

opened 2026-04-02 23:21:17 +00:00 by freemo · 2 comments

freemo commented

2026-04-02 23:21:17 +00:00

Owner

Metadata

Branch: task/ci-implement-dependency-caching
Commit Message: chore(ci): implement uv dependency caching between CI runs
Milestone: v3.8.0
Parent Epic: (to be linked — see orphan note below)

Description

The current CI pipeline does not cache dependencies between runs. This can lead to longer build times, especially for projects with a large number of dependencies.

We should implement a caching mechanism to store the uv cache between CI runs. This will significantly reduce the time it takes to install dependencies and speed up the overall CI process.

Area: CI/CD

Subtasks

Investigate different caching mechanisms that are compatible with our CI provider.
Implement the chosen caching mechanism in the CI configuration (e.g., using actions/cache or the built-in uv cache support).
Verify that the caching mechanism is working correctly and that it is reducing the build time.
Update CI documentation/comments to reflect the new caching strategy.

Definition of Done

The uv cache is cached between CI runs.
The build time is significantly reduced.
The CI pipeline runs successfully with the new caching strategy.
All nox stages pass.
Coverage >= 97%.

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

## Metadata - **Branch**: `task/ci-implement-dependency-caching` - **Commit Message**: `chore(ci): implement uv dependency caching between CI runs` - **Milestone**: v3.8.0 - **Parent Epic**: *(to be linked — see orphan note below)* ## Description The current CI pipeline does not cache dependencies between runs. This can lead to longer build times, especially for projects with a large number of dependencies. We should implement a caching mechanism to store the `uv` cache between CI runs. This will significantly reduce the time it takes to install dependencies and speed up the overall CI process. **Area**: CI/CD ## Subtasks - [ ] Investigate different caching mechanisms that are compatible with our CI provider. - [ ] Implement the chosen caching mechanism in the CI configuration (e.g., using `actions/cache` or the built-in `uv` cache support). - [ ] Verify that the caching mechanism is working correctly and that it is reducing the build time. - [ ] Update CI documentation/comments to reflect the new caching strategy. ## Definition of Done - [ ] The `uv` cache is cached between CI runs. - [ ] The build time is significantly reduced. - [ ] The CI pipeline runs successfully with the new caching strategy. - [ ] 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:22:25 +00:00

freemo commented

2026-04-02 23:23:08 +00:00

Author

Owner

⚠️ Orphan Issue — Manual Linking Required

This issue was created without a parent Epic. No CI/CD or Test Infrastructure Epic was found in the open issues at the time of creation. All existing [ci-pipeline-design] issues in this repository are similarly unlinked.

Action Required: A project maintainer must either:

Link this issue to an existing parent Epic by making this issue block that Epic (child blocks parent), or
Create a new Type/Epic for the ci-pipeline-design workstream and link all related issues to it.

Per CONTRIBUTING.md, orphan issues are not permitted — every Issue must be linked to a parent Epic or Legendary via Forgejo dependencies.

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

⚠️ **Orphan Issue — Manual Linking Required** This issue was created without a parent Epic. No CI/CD or Test Infrastructure Epic was found in the open issues at the time of creation. All existing `[ci-pipeline-design]` issues in this repository are similarly unlinked. **Action Required**: A project maintainer must either: 1. Link this issue to an existing parent Epic by making this issue **block** that Epic (child blocks parent), or 2. Create a new `Type/Epic` for the `ci-pipeline-design` workstream and link all related issues to it. Per `CONTRIBUTING.md`, orphan issues are not permitted — every Issue must be linked to a parent Epic or Legendary via Forgejo dependencies. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo commented

2026-04-02 23:31:08 +00:00

Author

Owner

Closing as duplicate of #1589 (dependency caching improvement). This CI caching improvement is already tracked.

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

Closing as duplicate of #1589 (dependency caching improvement). This CI caching improvement is already tracked. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo

2026-04-02 23:31:09 +00:00