TEST-INFRA: [ci-execution-time] Use a custom Docker image with pre-installed dependencies #3782

Open
opened 2026-04-06 06:17:52 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: task/ci-execution-time-custom-docker-image
  • Commit Message: feat(ci): use custom Docker image with pre-installed dependencies to reduce job overhead
  • Milestone: Backlog (see note below)
  • Parent Epic: #1678

Background and Context

The .forgejo/workflows/ci.yml workflow contains several jobs that repeat the same dependency installation steps (e.g., Node.js, uv, nox, Helm). This redundancy adds unnecessary overhead to each job and increases the overall CI execution time — directly counter to the goals of the parent Epic #1678 (CI Execution Time Optimization).

Creating a custom Docker image with all required dependencies pre-installed eliminates this repeated setup work, allowing each job to start executing immediately.

Proposal

Create a custom Docker image with all required CI dependencies pre-installed and publish it to a container registry. Update ci.yml to use this image as the base for all jobs, removing the redundant dependency installation steps.

Subtasks

  • Create a Dockerfile for the custom Docker image.
  • Pre-install all the required dependencies, including Node.js, uv, nox, and Helm.
  • Publish the Docker image to a container registry.
  • Update the ci.yml file to use the new Docker image.
  • Remove redundant dependency installation steps from individual CI jobs.
  • Verify all nox stages pass after changes.
  • Confirm coverage ≥ 97%.

Definition of Done

  • A custom Docker image is created and published to a container registry.
  • The ci.yml file is updated to use the new Docker image.
  • The dependency installation steps are removed from the individual jobs.
  • The overall CI execution time is reduced.
  • All nox stages pass.
  • Coverage >= 97%.

Backlog note: This issue was discovered during autonomous operation
on milestone v3.8.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**: `task/ci-execution-time-custom-docker-image` - **Commit Message**: `feat(ci): use custom Docker image with pre-installed dependencies to reduce job overhead` - **Milestone**: Backlog (see note below) - **Parent Epic**: #1678 ## Background and Context The `.forgejo/workflows/ci.yml` workflow contains several jobs that repeat the same dependency installation steps (e.g., Node.js, uv, nox, Helm). This redundancy adds unnecessary overhead to each job and increases the overall CI execution time — directly counter to the goals of the parent Epic #1678 (CI Execution Time Optimization). Creating a custom Docker image with all required dependencies pre-installed eliminates this repeated setup work, allowing each job to start executing immediately. ## Proposal Create a custom Docker image with all required CI dependencies pre-installed and publish it to a container registry. Update `ci.yml` to use this image as the base for all jobs, removing the redundant dependency installation steps. ## Subtasks - [ ] Create a Dockerfile for the custom Docker image. - [ ] Pre-install all the required dependencies, including Node.js, uv, nox, and Helm. - [ ] Publish the Docker image to a container registry. - [ ] Update the `ci.yml` file to use the new Docker image. - [ ] Remove redundant dependency installation steps from individual CI jobs. - [ ] Verify all nox stages pass after changes. - [ ] Confirm coverage ≥ 97%. ## Definition of Done - [ ] A custom Docker image is created and published to a container registry. - [ ] The `ci.yml` file is updated to use the new Docker image. - [ ] The dependency installation steps are removed from the individual jobs. - [ ] The overall CI execution time is reduced. - [ ] All nox stages pass. - [ ] Coverage >= 97%. --- > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.8.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
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#3782
No description provided.