TEST-INFRA: [ci-pipeline-design] Use a global uv cache #3583

Open
opened 2026-04-05 20:05:26 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: chore/ci-global-uv-cache
  • Commit Message: chore(ci): configure global uv cache dir for faster dependency installs
  • Milestone: Backlog
  • Parent Epic: #1678

Description

The noxfile.py uses uv as the venv backend, which is a significant performance improvement over virtualenv. To further optimize dependency installation times, a global uv cache should be implemented and shared across all nox sessions and CI runs.

By setting the UV_CACHE_DIR environment variable to a path that is cached by the CI system (e.g., .uv_cache), we can avoid redundant downloads and installations of the same package versions, leading to faster and more efficient CI pipelines.

Subtasks

  • Determine the optimal location for the global uv cache directory within the project structure.
  • Modify the CI workflow configuration to set the UV_CACHE_DIR environment variable.
  • Configure the CI system to cache the contents of the UV_CACHE_DIR between runs.
  • Verify that the cache is being used effectively by inspecting the CI logs.
  • Document the change in the project's development guide.
  • 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 UV_CACHE_DIR environment variable is set in the CI environment.
  • The CI system caches the uv cache directory between runs.
  • Dependency installation times in the CI pipeline are measurably reduced.
  • The change is documented in the project's development guide.
  • 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%.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.6.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-global-uv-cache` - **Commit Message**: `chore(ci): configure global uv cache dir for faster dependency installs` - **Milestone**: Backlog - **Parent Epic**: #1678 ## Description The `noxfile.py` uses `uv` as the venv backend, which is a significant performance improvement over `virtualenv`. To further optimize dependency installation times, a global `uv` cache should be implemented and shared across all nox sessions and CI runs. By setting the `UV_CACHE_DIR` environment variable to a path that is cached by the CI system (e.g., `.uv_cache`), we can avoid redundant downloads and installations of the same package versions, leading to faster and more efficient CI pipelines. ## Subtasks - [ ] Determine the optimal location for the global `uv` cache directory within the project structure. - [ ] Modify the CI workflow configuration to set the `UV_CACHE_DIR` environment variable. - [ ] Configure the CI system to cache the contents of the `UV_CACHE_DIR` between runs. - [ ] Verify that the cache is being used effectively by inspecting the CI logs. - [ ] Document the change in the project's development guide. - [ ] 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 `UV_CACHE_DIR` environment variable is set in the CI environment. - [ ] The CI system caches the `uv` cache directory between runs. - [ ] Dependency installation times in the CI pipeline are measurably reduced. - [ ] The change is documented in the project's development guide. - [ ] 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%. > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.6.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
freemo added this to the v3.7.0 milestone 2026-04-05 20:16:28 +00:00
freemo removed this from the v3.7.0 milestone 2026-04-06 23:38:02 +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#3583
No description provided.