-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins ver. 1.565
Jenkins.doQuietDown(boolean block, int timeout) blocks as long as there are jobs running. This is not what it says in the documentation and a less useful behavior in my point of view.
boolean block
usage="Block until the system really quiets down and no builds are running"
int timeout
usage="If non-zero, only block up to the specified number of milliseconds"
I suggest the implementation should do what it says in the doc, i.e. only wait timeout, then return even though jobs are still running.
This error should be easily exposed by a unit test...
- links to
[JENKINS-24914] Jenkins.doQuietDown(boolean block, int timeout) blocks while jobs running (incorrect doc)
Assignee | New: Daniel Beck [ danielbeck ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Remote Link | New: This issue links to "PR 1421 (Web Link)" [ 11802 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Progress [ 3 ] | New: Resolved [ 5 ] |
At first glace the code looks fairly straightforward and correct
https://github.com/jenkinsci/jenkins/blob/stable/core/src/main/java/jenkins/model/Jenkins.java#L2881
So you're specifying e.g. block=true timeout=10000 for the CLI command, and it waits for much longer than 10 seconds?