Deduplicate UV environment setup across CI steps #43

Closed
opened 2026-03-13 14:33:45 +00:00 by kert · 0 comments
Owner

Problem

Both lint and test steps independently run uv python pin && uv sync --dev && uv pip install -e . (~30-60s each). Since test will depend on lint (after issue #42), the workspace already has the installed environment.

Fix

Set UV_PROJECT_ENVIRONMENT=.venv so the virtualenv lives in the shared workspace. Only the first step (lint) runs the full install; subsequent steps reuse it.

Acceptance criteria

  • CI pipeline total time reduced (test step skips uv sync)
  • Both lint and test use the same dependency versions
  • No test failures from missing packages
## Problem Both lint and test steps independently run `uv python pin && uv sync --dev && uv pip install -e .` (~30-60s each). Since test will depend on lint (after issue #42), the workspace already has the installed environment. ## Fix Set `UV_PROJECT_ENVIRONMENT=.venv` so the virtualenv lives in the shared workspace. Only the first step (lint) runs the full install; subsequent steps reuse it. ## Acceptance criteria - CI pipeline total time reduced (test step skips uv sync) - Both lint and test use the same dependency versions - No test failures from missing packages
kert added this to the P9: CI/CD Unification milestone 2026-03-13 14:33:45 +00:00
kert added the quality label 2026-03-13 14:33:45 +00:00
kert closed this issue 2026-03-13 14:48:43 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#43