I think that's a great idea. The main downsides I see are: * the multibranch plugin (which I use already) is pretty flaky. I find it will sometimes reset all the branches to be enabled even though I try to disable old branches to get them out of the view * if you create a lot of branches you end up with a huge number of workspaces and disk space which never goes away. In svn the solution to that is to create an 'archived' folder and move old branches/tags there. You can't do that in git though since it is more rigid in how it handles tags/branches. * The UI gets cluttered in Jenkins
But I love the idea of a tag driving the release process and the version naming is embedded in the tag name itself. On Thursday, 4 January 2018 16:11:14 UTC+11, Steven Foster wrote: > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/13b94c91-3864-4a1e-acd8-f450bfb87078%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
