Skip to content

ci: move the CI registry to ghcr.io/ai-openshell/openshell - #5817

Queued
SDAChess wants to merge 3 commits into
mainfrom
ci/4554-ci-registry/SDAChess
Queued

SDAChess wants to merge 3 commits into
mainfrom
ci/4554-ci-registry/SDAChess

Conversation

@SDAChess

Copy link
Copy Markdown
Contributor

Summary

After the transfer to ai-openshell/openshell, the repository token cannot push to or pull from ghcr.io/nvidia/openshell, and ghcr.io/nvidia/openshell/ci is an internal NVIDIA package. This PR moves the CI registry to ghcr.io/ai-openshell/openshell so CI builds and pulls its images in the new org.

Draft until the transfer. It merges right after the transfer, ahead of other PRs, because Branch Checks and Helm Lint fail everywhere until it lands.

Related Issue

Refs #4554

Changes

  • ci-image.yml pushes the CI job image to ghcr.io/ai-openshell/openshell/ci.
  • build-docker-image tags the gateway, sandbox and supervisor E2E images and verifies their SBOMs under the new registry.
  • The Docker, Podman and Kubernetes E2E lanes, setup-e2e-kind, prepare-integration-inputs and release-qualification pull from the new registry.

To follow on this branch after the transfer:

  1. Dispatch ci-image.yml on this branch to publish the first ghcr.io/ai-openshell/openshell/ci image.
  2. A maintainer makes the openshell/ci package public; fork PR runs pull it without credentials.
  3. Add a commit that repins the 12 job containers still on ghcr.io/nvidia/openshell/ci (Branch Checks, Helm Lint, cargo-deny, Release Dev, Release VM Kernel, the disabled GPU E2E) to the new image by digest.

With step 3 in place, this PR's own required checks can pass. If it has to merge before step 3, it needs a maintainer bypass, because its jobs cannot pull the old image from the new org.

Release promotion references to ghcr.io/nvidia/openshell (release-dev, release-publish, release-helm-oci, release-canary, prepare-upgrade-source) and the E2E script registry defaults are handled in separate PRs.

Testing

  • actionlint and zizmor report no new findings against main
  • Branch Checks, Helm Lint and E2E pass after the transfer, with the repinned CI image

Checklist

  • Follows Conventional Commits
  • Commits are signed off (DCO)
  • Architecture docs updated (if applicable)

@github-actions github-actions Bot added the state:accepted A maintainer decided OpenShell should pursue this issue label Nov 20, 2026
@github-actions

Copy link
Copy Markdown

Compatibility review (advisory)

New or updated breaking changes; see the full report for all findings.

1. api-behavior — No explicit risk acceptance found

Qualification-summary publication moves from ghcr.io/nvidia/openshell/qualification to ghcr.io/ai-openshell/openshell/qualification without retaining the documented endpoint.

  • Impact: Release-evidence consumers using the documented OCI reference cannot retrieve newly generated qualification-summary.json files there, although Actions artifacts remain available.
  • Action: Preserve the documented qualification-summary references through dual publication or a compatible registry alias for v0.1.10, and provide notice and actionable migration guidance before retiring them in a permitted minor train.
  • PR: ci: move the CI registry to ghcr.io/ai-openshell/openshell #5817
Review details
  • Execution: complete
  • Candidate: PR #5817 (fbdc54e351962b8eb88d40c177041335840ce714)
  • Baseline: 00390c8acb1f0d0055400124e957e85efa0c5106 (00390c8acb1f0d0055400124e957e85efa0c5106)
  • Reviewed: rust-sdk, python-sdk, typescript-sdk, api-behavior, cli, configuration, policy, helm, state

Advisory review; publication gates are unchanged.

Branch check run

@SDAChess
SDAChess marked this pull request as ready for review November 20, 2026 13:40
The moved repository's token cannot push to ghcr.io/nvidia/openshell. Build
the CI job image and the SHA-tagged gateway, sandbox and supervisor E2E
images under ghcr.io/ai-openshell/openshell, and pull them from there in
the E2E lanes, tmachine input preparation and release qualification.

Refs #4554

Signed-off-by: Simon Scatton <sscatton@nvidia.com>
The E2E harness falls back to ghcr.io/nvidia/openshell for SHA-tagged CI
images, which the moved repository no longer publishes. Point the Docker,
Podman and Kubernetes harness defaults, the TESTING.md variable table and
the test-guest cache example at ghcr.io/ai-openshell/openshell.

Refs #4554

Signed-off-by: Simon Scatton <sscatton@nvidia.com>
The moved repository cannot pull the internal ghcr.io/nvidia/openshell/ci
package. Pin every job container to the CI image built in the new home,
ghcr.io/ai-openshell/openshell/ci, by digest.

Refs #4554

Signed-off-by: Simon Scatton <sscatton@nvidia.com>
@SDAChess
SDAChess force-pushed the ci/4554-ci-registry/SDAChess branch from 82e753b to f86a84e Compare November 20, 2026 14:15
@SDAChess
SDAChess added this pull request to the merge queue Nov 20, 2026
Any commits made after this event will not be merged.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

state:accepted A maintainer decided OpenShell should pursue this issue

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants