![]() |
|
|
|
|
Issue Type:
|
![New Feature]() New Feature
|
|
Assignee:
|
Unassigned |
|
Components:
|
next-executions |
|
Created:
|
08/Jan/14 9:35 AM
|
|
Description:
|
I use the next executions to estimate whether I need to run a manually triggered build after infrastructure changes for a job, which is triggered all 4 hours anyway (to avoid it running on multiple nodes nearly at the same time).
(I know there are all kinds of plugins and settings to avoid concurrent builds, but we cannot use them for this job, as it actually makes sense to have concurrent builds, if people really changed things in between).
Currently I have to compare the next execution time against the reported page creation time to see how far away the next job is (which gets even more complicated due to the server being in a timezone 4.5 hours away). I therefore suggest to enhance the output to something like
<job name> <next starting time> (in <time away>)
e.g.
regular maintenance 18:05:00 (in 01:20:34)
Feel free to leave seconds away, or to only create such output for jobs in the next n hours. Or make it just a tooltip on the absolute time, if you feel that the space might not be sufficient.
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Minor]() Minor
|
|
Reporter:
|
Michael Keppler
|
|
|
|
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/groups/opt_out.
