Are there any established best practices for testing out changes to Jenkins jobs before taking them live? After causing a few false alarm build breaks by messing up important jobs, we now create a sandbox version of a job to try config changes, but it can be tricky when they're in a chain of triggered builds, and copying the config back to the "real" job has the potential to introduce errors. Additionally, we put everything we reasonably can in the projects being built, but some stuff has to live in Jenkins.
I'm sure we'll eventually get to a point where the jobs change very rarely, but we're still learning the best ways to set things up, and changes are fairly frequent. Has anyone come up with a way they're happy with? Thank you, Todd Greer Director of Development, Affinegy, Inc.
