|
||||||||
|
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.
Javadoc documentation:
> "True to keep builds of this project in queue when upstream projects are building. False by default to keep from breaking existing behavior."
Jobs in the queue and pending jobs (assigned to executor, but not started) have Run.State.NOT_STARTED status (there's also Run.State.BUILDING status). Build::isBuilding() returns try for both statuses, so there's a risk of confusion.
Paul, my bad. Your case is valid.
The handling of the restrictions is based on Queue::getUnblockedItems(), so Jenkins ignores dependencies on blocked tasks like throttled runs.
We just need to decide if it is a functional or a documentation bug. I'd vote fore the first option.