Plugin Information |
---|
View Exclusive Execution on the plugin site for more information. |
Allows a job to be executed when no other jobs are running.
Possible uses
Execute a backup job: because backup-plugin cannot be scheduled, then I have created my own Jenkins backup script. To run it from Jenkins I crated a 'maintenance' job that must execute when there are no other job running, so this plugin can help perform this backup procedure.
How it works
When this option is enabled, then for every build one pre-build and one post-build steps are executed:
pre-build steps:
- The plugin will initiate a shutdown mode which means that no other jobs can be started.
- It waits until every job except this one has finished, unless it is indicated not to wait through optional flag.
- Then it starts to execute the job.
post-build steps (executed always even if the build is not succesful):
- Jenkins shutdown mode is canceled
Version History
Development
Version 0.8 (Feb 4, 2015)
- issue #26175 Optional lenient mode added. If activated exclusive-execution job will not wait for currently running jobs to perform build steps (i.e. activate shutdown mode immediately).
- issue #26351 Spanish translation added.
- issue #24854 Shutdown mode is interrupted now if job is canceled in pre-build phase.
- Fernando Miguélez becomes maintainer of the plugin
Version 0.7 (Jul 31, 2011)
- Major refactoring by Sam Tavakoli
Version 0.6 (Feb 25, 2011)
- Improve error handling
- Translation update (Japanese)
Version 0.2 (Apr 15, 2010)
- Removed limitation of execution on master
- Removed useless dependencies from pom.xml that create a huge hpi file
Version 0.1 (Apr 13, 2010)
- Initial release
Warning
Unfortunately the hpi file is huge (~17 MByte)... sorry
- Job must be executed on master
5 Comments
Unknown User (r.oosterholt)
Jamil Ahmed
How do I activate this on a Build Flow job? I don't see any new options on the job's configure page and there aren't any screenshots showing what to do on this page. I see the option on a regular job's page though.
Prathyusha Duvvuru
Hello Jamil,
Did you get any hint to use this plugin in pipeline job?
Jonas Hommel
Is there a possibilty to extend this plugin in a way, that some slaves (signed by nodename or label) will not be observed for running jobs? Example: I have a master with to types of slaves (eg. TypeA and TypeB). I want a job running on master exclusively, when no other jobs are running on master and "TypeA"-Slave. But the ExclusiveJob should be allowed to run, if still some Jobs are running on TypeB-Slave.
Sven Appenrodt
Is it possible to add an option, to allow downstream jobs, add multiconfiguration-project or pipeline support? Like: Lenient shutdown plugin
My problem: i have several nodes where a maintenance-script will be executes. Currently 1'll do it by using a "Node" parameter, that triggers the job multiple times and each job set the jenkins in shoutdown mode and canceles it on finish. Currently there is no way e.g. using pipeline or axises to run the "maintenance-scripts" on each node concurrent.
Solution 1) running multi-config: requires ability to set/cancel the shutdownmode for the matrix-job, not the axis-jobs and allow downstreams to finish
Solution 2) running pipeline: requires ability to set/cancel the shutdownmode for a pipeline and allow downstreams to finish
Any other ideas?