I have been using the multibranch project's tag build functionality to achieve this. An environment variable is provided when running a tag build, so the pipeline can have a stage which checks for the presence of that variable. Using multibranch to build a single branch seems a little counter intuitive, but the branch api provides convenience in other areas and allows other branches to be added later with ease.
The release process becomes something like: Push a tag -> Multibranch project detects tag and creates a job for that tag -> Manually run that tag job to perform a release (somewhat like a button on a build but a little more clear and structured imo) -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/4e7bcd25-4c80-4972-aa5b-3a34132340d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
