|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Cancelling the existing low priority job may not be nice, but it should be the easiest to implement as the capability to manually cancel a job already exists.
The prospect of pausing, then resuming a low priority job looks nice, however there may be reasons why this can't happen which are beyond the control of Jenkins. For example the job may need exclusive use of a build slave, using hard coded paths that would collide if two jobs run concurrently. Even if one job is paused, the new high priority job risks being contaminated by the paused job or alternatively the low priority job may be upset by changes to its environment caused by the high priority job.
Can we have the ability to cancel the low priority job?
When pausing JENKINS-4683 becomes available, then make that an option as well. Let's give the user the choice rather than delaying a solution to this bug to wait for pause functionality.