[debug] Add sync-to-nexus workflow + Tekton pipeline trigger#23
Closed
l-qing wants to merge 2 commits into
Closed
Conversation
workflow_dispatch only registers workflows on the default branch, so until this file lands on master we cannot manually trigger it. Adding pull_request (paths-scoped to this file) lets us iterate inside a PR against master without merging first — GitHub picks up the workflow content from the PR head branch for pull_request events. The TAG env gains a pull_request fallback to a known-good debug tag because github.ref_name on PR is the head branch name, not a release tag.
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.
Summary
.github/workflows/sync-to-nexus.ymlthat, on every `v*-alauda-*` tag push, creates a Hub-resolved Tekton PipelineRun on the in-cluster ARC runner to mirror the GitHub Release assets to internal Nexus.How this is being tested
Path A (in-namespace pipeline + sample PipelineRun): ✅ green end-to-end on the integration cluster — assets land at `https://build-nexus.alauda.cn/repository/alauda/devops/github-releases/AlaudaDevops/yq/v4.47.2-alauda-19/\` and `.../latest/`, `_meta.json` written, Tekton overview-markdown shows clickable Nexus UI deep-links.
Path B (this PR): triggering via `pull_request` to validate the GitHub Actions trigger surface end-to-end before the Tekton pipeline merges into the catalog and we flip the `pipelineRef` to `resolver: hub`.
Test plan
Out of scope for this PR
🤖 Generated with Claude Code