![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Nicolas De Loof
|
|
Attachments:
|
Jenkins.png |
|
Components:
|
build-cause-run-condition, build-environment, build-flow, build-pipeline |
|
Created:
|
18/Jul/13 7:45 AM
|
|
Description:
|
Hello!
Environment: We have several jobs for each executor. So, submitted builds often wait for the next available executor.
I often perform the following scenario:
- Commit important changes, which build result is urgent.
- Submit this build for execution in queue (to just increase its priority in queue).
- Remove low-priority jobs from build queue.
- Stop execution of not-important job on the available executor.
I guess this scenario could be automated by adding new button in jobs table.
My expectations for this control are:
1. Stop current execution on the available executor.
2. Start execution of the target job immediately.
|
|
Project:
|
Jenkins
|
|
Labels:
|
build
queue
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Artem Morozov
|
|
|
|
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/groups/opt_out.
