OK, I've made a small amount of progress. I've learned that: 1. The release plugin doesn't work with pipeline 2. The promoted build plugin doesn't work with pipeline 3. Some users are using the "input" command to cause the build to hang for a few days, and then be able to make a release. This mostly sucks. 4. No one else seems to have solved this problem either.
Now I could make a separate pipeline just for releases, but that seems clunky. What I'm trying now is a parameterised build to allow me to tick a checkbox for "release" and trigger optional stages within the pipeline. On Thursday, 28 December 2017 17:30:08 UTC+11, Ari Maniatis wrote: > > I'm starting to experiment with Jenkinsfile configuration and its mostly > coming together. Probably the hardest thing is sorting out which > instructions are for the old script syntax and which for the new > declarative syntax. Probably a few years from now stackoverflow will have > more correct answers than wrong ones. > > Anyhow, I'm stuck on understanding how we are supposed to perform a > release. Today we use the release plugin so there is a 'release' button > directly in the UI which performs different (additional) gradle steps after > the build is successful. In addition, there is a field to type in a version > number for this release. > > All that works well, so something similar would be great. I'm also open to > other ideas like committing a tag in svn, but I can't see how that would > work either since I'm only tracking one branch in jenkins. Checking out > every branch would be horrendous. > > Thanks for any pointers. > -- 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/191b31af-380f-4bb9-ad42-b96554f8104d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
