|
||||||||
|
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/groups/opt_out.
As an additional note, if there are numerous projects configured to use a Matrix build then the master machine can be really hobbled as it tries to simultaneously sync all the projects that exist. This sync phase does not get queued because it doesn't require an executor to run, it's just the master preparing itself to tell the slaves to do something.
As a result, the master machine ends up crawling as the disk usage goes through the roof from many (large) projects syncing at once.