Skip to content

ci: use registry cache for container builds#2491

Draft
kajalj22 wants to merge 1 commit into
mainfrom
cursor/fix-container-build-cache-4026
Draft

ci: use registry cache for container builds#2491
kajalj22 wants to merge 1 commit into
mainfrom
cursor/fix-container-build-cache-4026

Conversation

@kajalj22
Copy link
Copy Markdown
Contributor

What does this PR do ?

Switches the container build job from inline BuildKit cache to the reusable workflow's registry-backed cache. This lets fresh/ephemeral build runners reuse the expensive Docker layer that runs uv sync across dependency extras.

Issues

Linear: AUT-492

Usage

N/A - CI workflow change only.

Before your PR is "Ready for review"

Pre checks:

  • Make sure you read and followed Contributor guidelines
  • Did you write any new necessary tests? Workflow syntax validation only; no runtime code changed.
  • Did you run the unit tests and functional tests locally? Visit our Testing Guide for how to run tests
  • Did you add or update any necessary documentation? No docs needed for this CI-only change.

Additional Information

Validation run locally:

  • python3 YAML parse/assertion for .github/workflows/cicd-main.yml
  • git diff --check

actionlint and Docker are not installed in this cloud environment, so a full container build must run in CI.

Linear Issue: AUT-492

Open in Web Open in Cursor 

Signed-off-by: Cursor Agent <cursoragent@cursor.com>

Co-authored-by: kajalj22 <kajalj22@users.noreply.github.com>
@copy-pr-bot
Copy link
Copy Markdown

copy-pr-bot Bot commented May 13, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions github-actions Bot added the CI Relating to CI label May 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CI Relating to CI

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants