|
||||||||
|
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/groups/opt_out.
This has definitely have to do with the fact that we have large amount of jobs (around 185) configured on a single Master Jenkins.
On a test installation with significantly smaller number of jobs the delay is unnoticeable.
When calling a job directly through post-commit hooks it starts building instantaneously, however if Jenkins has to scan through the job configs to find the matching job the delay becomes unacceptable.