TEST-INFRA: [ci-pipeline-design] Add dependency caching for uv #3299

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

The CI pipeline re-installs dependencies on every run. We should configure a cache for uv to speed up the process.

Metadata

  • Branch: test-infra/ci-pipeline-design/add-uv-dependency-caching
  • Commit Message: chore(ci): add uv dependency caching to CI pipeline
  • Milestone: (backlog — see note below)
  • Parent Epic: #3204

Subtasks

  • Identify the CI pipeline configuration file(s) where uv is invoked
  • Research the correct caching strategy for uv (e.g., cache ~/.cache/uv or the virtual environment)
  • Add a cache step to the CI pipeline before the uv install step
  • Verify that the cache is correctly restored on subsequent runs
  • Confirm that cache invalidation works correctly when pyproject.toml or uv.lock changes
  • Update CI documentation if applicable

Definition of Done

  • A cache for uv dependencies is configured in the CI pipeline
  • CI pipeline run time is measurably reduced after the cache is warm
  • Cache is invalidated correctly when dependency files change
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone . 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

The CI pipeline re-installs dependencies on every run. We should configure a cache for uv to speed up the process. ## Metadata - **Branch**: `test-infra/ci-pipeline-design/add-uv-dependency-caching` - **Commit Message**: `chore(ci): add uv dependency caching to CI pipeline` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #3204 ## Subtasks - [ ] Identify the CI pipeline configuration file(s) where `uv` is invoked - [ ] Research the correct caching strategy for `uv` (e.g., cache `~/.cache/uv` or the virtual environment) - [ ] Add a cache step to the CI pipeline before the `uv` install step - [ ] Verify that the cache is correctly restored on subsequent runs - [ ] Confirm that cache invalidation works correctly when `pyproject.toml` or `uv.lock` changes - [ ] Update CI documentation if applicable ## Definition of Done - [ ] A cache for `uv` dependencies is configured in the CI pipeline - [ ] CI pipeline run time is measurably reduced after the cache is warm - [ ] Cache is invalidated correctly when dependency files change - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone <current active>. 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

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — CI optimization is useful but not blocking any milestone.
  • Milestone: v3.8.0 — CI pipeline improvements belong in v3.8.0.
  • MoSCoW: Could Have — Dependency caching is a nice-to-have optimization. It improves CI speed but doesn't affect functionality.
  • Parent Epic: #1678 (CI Execution Time Optimization) — references parent Epic #3204 in body, but #1678 is the main CI optimization Epic.

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — CI optimization is useful but not blocking any milestone. - **Milestone**: v3.8.0 — CI pipeline improvements belong in v3.8.0. - **MoSCoW**: Could Have — Dependency caching is a nice-to-have optimization. It improves CI speed but doesn't affect functionality. - **Parent Epic**: #1678 (CI Execution Time Optimization) — references parent Epic #3204 in body, but #1678 is the main CI optimization Epic. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
freemo added this to the v3.8.0 milestone 2026-04-05 09:43:17 +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#3299
No description provided.