![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
core |
|
Created:
|
07/Oct/14 8:22 PM
|
|
Description:
|
We typically use a safe-restart after updating Jenkins and its plugins to the latest and greatest. This freezes our executors and prevents any new jobs from starting while waiting patiently for existing jobs to finish. This is a great feature, and much easier than watching the queue and restarting by hand when safe.
However, we have some jobs that typically last 25-40 minutes and a few intense tasks which can last longer than 1 hour. Triggering a safe-restart while one of these jobs are running can block progress for much longer than we'd prefer, and we often have to cancel the safe-restart to allow other (faster and higher-priority) jobs to execute.
I would like to request a 'nice-restart' feature which, like safe-restart, will only act when the executors are free and no builds are running. Unlike safe-restart, this mode will let new jobs trigger and execute as normal while it waits patiently for a completely free build queue.
This would allow our Tools team to perform low-priority upgrades at our convenience without delaying high-priority build tasks the Dev team depends on.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
James LeVeque
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
