I’m using a Jenkins instance to execute Gradle builds and publish distribution snapshots to Artifactory via the Jenkins Artifactory plugin. This all works swimmingly, and I’d like to expand our use case to include the release staging functionality (we have Artifactory Pro). However, I’m having difficulty wrapping my head around the intended workflow. As I understand it:
When we’re close to a delivery date, we “stage” a release. This involves (a) specifying the release version number and cutting a new build, which then gets published into some intermediate, staging repository, and (b) specifying the next development version number, which gets committed back into the source branch. The “staged” release amounts to a release candidate. The idea is that it should get focused testing, and, if all goes well, it gets “promoted” — essentially copied — from the intermediate, staging repository into a release repository from which it can be grabbed for use in production environments. Where I’m struggling with this is understanding the intended workflow for the much-more-common case where testing of the RC doesn’t go well, and we have to accept a few changes and cut another RC. The staging plugin allows for a “roll back” status, but this only affects the artifact metadata in Artifactory; it doesn’t, for example, reverse the commit to the source branch incrementing the next development version number. Moreover, if we re-use the same version number for the “new” RC, then the previous RC will get overwritten unless we move it out of the staging repo; but if we don’t — for example, if we identify our RCs by calling them “rc1”, “rc2”, etc. — then that extraneous information will stay in the RC name and in the generated poms when we eventually promote it to a release. Can some kind soul provide some guidance, here? Thanks, -Brett ------------------------------------------------------------------------------ _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
