I see the following suggested rollback procedure here: https://wiki.jenkins-ci.org/display/JENKINS/Deploy+Plugin
1. Install the Copy Artifact Plugin<https://wiki.jenkins-ci.org/display/JENKINS/Copy+Artifact+Plugin> 2. Create a new job that you will trigger manually only when needed 3. Configure this job with a build parameter of type "Build selector for Copy Artifact", and a copy artifact build step using "Specified by build parameter" to select the build. 4. Add a post-build action to deploy the artifact that was copied from the other job If I read that right, you need to have the artifacts for the build you want to roll back to previously archived and not discarded. I'm looking to potentially be able to rollback to builds with artifacts built from a git repo that aren't archived. I can see it being pretty easy to copy the last commit SHA for the targeted build as a build parameter. But is it easy to just store the SHA with a build and have this "rollback job" read that in automatically? Is there a simpler/standard way to do this? -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
