|
||||||||
|
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.
Hi,
I'm using Jenkins 1.532.2 and am seeing the same error... but maybe slightly different?
You tell me - quite happy to dump logs and the like (will look at the docs and add another comment later).
Our primary Jenkins master is running on a Google VM, with the slaves running on other Google VM's and connected/registered via swarm plugin.
We use REST API to launch jobs and monitor output - so while we seem similar problem, its also sorta the same![]()
The REST API returns the error mentioned so many times above... pretty stack trace output partially into the build.
HOWEVER, once the API has returned the error text, our app stops polling for console output. At that point the SAME build seems to start logging again in the normal Jenkins build console... and when you add the initial logging retrieved via REST and the new logging that started upon failure, we see the build actually did complete. (REST log + Console log = Entire log)
Doug
As mentioned above, I'll try to get some official logs and attach them later.