Let the jobs trigger when they will. But force the jobs to run only on certain nodes (such as by using a label). Then, when configuring the nodes, set the availability to “Take this slave on-line according to a schedule”. Now, when you don’t want the jobs to be running, they’ll queue up waiting for a node they can run on to fire up.
--Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ari Maniatis Sent: Wednesday, June 13, 2012 6:15 AM To: jenkinsci-users@googlegroups.com Subject: Restricting builds from running at certain times of the day I have a Jenkins server which is triggered by the usual svn hooks on every commit. However I also have some very long running jobs which I only want to run overnight, when we have spare CPU capacity. For those jobs I have unticked the option: [ ] Trigger builds remotely (e.g., from scripts) But it would appear that that option does not apply to the subversion trigger URL ( /server/subversion/${UUID}/notifyCommit?rev=$REV ). How do I ensure that some jobs are NOT triggered by the subversion hook along with all the others? I want them to run on a timed schedule or polling instead. The information in this message is for the intended recipient(s) only and may be the proprietary and/or confidential property of Litle & Co., LLC, and thus protected from disclosure. If you are not the intended recipient(s), or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any use, dissemination, distribution or copying of this communication is prohibited. If you have received this communication in error, please notify Litle & Co. immediately by replying to this message and then promptly deleting it and your reply permanently from your computer.
