|
||||||||||||||
|
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.
Nobody is interested in this feature, so resolving as Won't Fix.
Also, it's not obvious why a new build shouldn't be queued after the current build checked out from SCM and a new change was detected.
Querying SCM every minute is unnecessarily expensive anyway, if you need immediate builds, just switch to post-commit hook notifications.
Also, behavior would need to be determined for parallel build projects.