I've run a groovy script to disable all jobs before. Then, I just enable the jobs I want to run. The problem with that, though is that Pipeline jobs can't be disabled. So, I normally have to go into the test instance and manually remove the triggers on the Pipeline jobs to keep them from running. I'm sure a script could do this, too, but I haven't seen one.
On Monday, November 7, 2016 at 8:04:51 AM UTC-6, Michael Giroux wrote: > > We have a large jenkins configuration with 1700 jobs. We have two use > cases in which the configuration is copied. We make a copy of the > configuration prior to any upgrade: > > 1. for purposes of testing new version and plugins prior to an upgrade > 2. to have a running instance of the previous version to allow "emergency > builds" for projects that will not build in new version after an upgrade. > > In both of these use cases, we have two copies of Jenkins running at the > same time (on different ports of course), the old version, and the new > version. In either case, we want to disable the build triggers for one of > the instances. We do not want two copies of jenkins building the same > project based on polling, or due to upstream builds and/or snapshot changes. > > We can use "prepare to shutdown" to suspend one instance. But if we > cancel shutdown to allow a specific build to be run, the flood gates open. > > It would be helpful if there was an option to allow manual builds even > when "prepare to shutdown" is in effect. Or, as the subject line suggests, > an option to disable triggers. Such an option should have an initial state > set by a system property allowing us to launch Jenkins with the option > initially on or off. > > Similar requests have been made previously: > http://jenkins-ci.361315.n4.nabble.com/Suspend-Plugin-td1599530.html > > http://stackoverflow.com/questions/1299180/can-i-disable-hudsons-automatic-scheduled-builds-all-at-once > > I would be interested in hearing how other users handle this case, > especially case #2 in which we wish to have the old instance of Jenkins > available to run builds that might not execute in the new version. > > Michael > > > -- 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/88fb59b0-ed81-47f2-8012-315f554d5f7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
