Nmailhot/nixl release pipeline - #1795
Closed
nv-nmailhot wants to merge 4 commits into
Closed
nv-nmailhot wants to merge 4 commits into
nv-nmailhot wants to merge 4 commits into
Conversation
ci.yml now runs builds + wheel uploads natively on GitHub Actions (self-hosted velonix runners), so the GitLab bridge is redundant. Remove build_validation.yml (repo mirror + .gitlab-ci.yml pipeline trigger) and its mirror_repo.sh helper. GPU tests stay deferred until ci.yml's ENABLE_GPU_CI jobs get real GPU runners. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a tag-gated release path: RELEASE_BUILD, scan, and upload jobs now also fire on refs/tags/v* (an RC/release tag), and a new trigger-gitlab-nspect job POSTs to the nixl-ci GitLab pipeline (PIPELINE_TYPE=rc, NSPECT_ID=NSPECT-WO64-8O3P, wheel version, rc tag) so nSpect/scans run GitLab-side against the wheels just uploaded to Artifactory. Modeled on dynamo's trigger-gitlab-release-pipeline; trigger token + URL come from the GITLAB_NIXL_* secrets in the release env. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Lets the RC nSpect/scan pipeline be triggered against a nixl-ci feature branch before it's merged to main, via repo variable NIXL_CI_REF (defaults to main). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The trigger job POSTs to gitlab-master.nvidia.com, which the AWS velonix builder runners cannot resolve. Move it to the gitlab_ci_runners org runner group (same one dynamo's release trigger uses), which has NVIDIA-internal reach. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
nv-nmailhot
added a commit
that referenced
this pull request
Jun 23, 2026
#1806) …t of #1795) The remaining changes from #1795, adapted to the release/** RC model: - Remove the GitLab bridge: build_validation.yml (repo mirror + .gitlab-ci.yml trigger) and mirror_repo.sh — superseded by the native ci.yml. - Add trigger-gitlab-nspect to ci.yml: on a push to a release/** branch (a PR merged into release/<x.y.z>), trigger the nixl-ci GitLab pipeline (PIPELINE_TYPE=rc) to run the wheel scan + nSpect registration (NSPECT-WO64-8O3P) against the wheels just uploaded to Artifactory. Runs on the gitlab_ci_runners group (internal reach); WHEEL_VERSION comes from the version job; NIXL_CI_REF selects the nixl-ci branch (defaults to main). (#1795 gated this on v*-rc tags; re-gated for the release/** model.) ## What? _Describe what this PR is doing._ ## Why? _Justification for the PR. If there is an existing issue/bug, please reference it. For bug fixes, the 'Why?' and 'What?' can be merged into a single item._ ## How? _It is optional, but for complex PRs, please provide information about the design, architecture, approach, etc._ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Removed deprecated validation workflow and repository mirror synchronization script * Enhanced release pipeline with automated nSpect registration and validation for published release builds <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
dpressle
pushed a commit
that referenced
this pull request
Jun 24, 2026
#1806) …t of #1795) The remaining changes from #1795, adapted to the release/** RC model: - Remove the GitLab bridge: build_validation.yml (repo mirror + .gitlab-ci.yml trigger) and mirror_repo.sh — superseded by the native ci.yml. - Add trigger-gitlab-nspect to ci.yml: on a push to a release/** branch (a PR merged into release/<x.y.z>), trigger the nixl-ci GitLab pipeline (PIPELINE_TYPE=rc) to run the wheel scan + nSpect registration (NSPECT-WO64-8O3P) against the wheels just uploaded to Artifactory. Runs on the gitlab_ci_runners group (internal reach); WHEEL_VERSION comes from the version job; NIXL_CI_REF selects the nixl-ci branch (defaults to main). (#1795 gated this on v*-rc tags; re-gated for the release/** model.) ## What? _Describe what this PR is doing._ ## Why? _Justification for the PR. If there is an existing issue/bug, please reference it. For bug fixes, the 'Why?' and 'What?' can be merged into a single item._ ## How? _It is optional, but for complex PRs, please provide information about the design, architecture, approach, etc._ <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Removed deprecated validation workflow and repository mirror synchronization script * Enhanced release pipeline with automated nSpect registration and validation for published release builds <!-- end of auto-generated comment: release notes by coderabbit.ai --> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What?
Describe what this PR is doing.
Why?
Justification for the PR. If there is an existing issue/bug, please reference it. For
bug fixes, the 'Why?' and 'What?' can be merged into a single item.
How?
It is optional, but for complex PRs, please provide information about the design,
architecture, approach, etc.