|
||||||||
|
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.
FWIW it's a hard-coded 300 seconds as per
https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L199
I have some difficulty imagining this needing to be longer, but it's certainly doable, at least via the usual System property approach for Options Nobody Should Ever Need Unless In Really Weird Situations:
https://wiki.jenkins-ci.org/display/JENKINS/Features+controlled+by+system+properties
Would that be acceptable?