|
||||||||
|
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.
Thanks for your feedback Daniel.
nextBuildNumber at the moment holds 8610 - which is true having a look at the web console https://ci.owncloud.org/job/pull-request-analyser-ng-simple/
To me this feels like some runtime/concurrency issue as soon as too many builds are triggered the same time.
This job is hooked up with github and jobs are being kicked off as soon as a pull request is created or new commits are pushed to the branches.
As desribed in the environment field - this can be up to 30 jobs running in parallel. Under these circumstances the executors die.
Any specific logger category of interest to analyse this issue?
THX