kubesphere / kubesphere/ks-devops
For a multi-branch Pipeline, the tag cannot be triggered automatically
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 164
- Forks
- 140
- PR merge metrics
- No merged PRs in 30d
Description
For some use cases, we build the container image once a new git tag is created. According to the feature of Jenkins, you will see the log output like this:
No automatic build triggered for v0.0.2
See the details from the changelog of github-branch-source-plugin
Open question
- How to support triggering a new tag automatically?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the referenced github-branch-source-plugin changelog entry and the Jenkins multi-branch Pipeline tag behavior first. Trace how this repository integrates that behavior; done means a new Git tag triggers the intended Pipeline automatically, with a documented or tested verification path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100