[CI] Add manual Windows container publisher - #11144
Conversation
2058153 to
1298e8e
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 SummarySummary by CodeRabbit
WalkthroughChangesThe pull request adds a manually triggered workflow that validates the internal package and then publishes the Windows container image through a pinned reusable workflow. Windows container publishing
Merge Risk: ⚪ Minimal · up to This adds a manually triggered, narrowly scoped Windows container publishing workflow with no actionable merge-blocking risk remaining after normal checks and review. Comment |
Description
Related: rapidsai/devcontainers#760
Adds an on-demand workflow that builds, tests, and publishes the full Windows
devcontainer matrix to the internal
ghcr.io/nvidia/cccl-windows-containerspackage.The workflow:
packages: writeonly to the reusable publishing job; andThe reusable workflow is pinned to the exact tested head of devcontainers #760.
Keep this PR in draft until that dependency merges, then update the pin if its
merge strategy produces a different commit.
Before the first dispatch, the package settings must grant
NVIDIA/ccclWriteunder Manage Actions access.
Validation
pre-commit run --files .github/workflows/publish-windows-containers.ymlactionlint .github/workflows/publish-windows-containers.ymlChecklist