Status: Open (View Workflow)
Environment:Jenkins: 2.18 (from pkg.jenkins-ci.org/debian apt repo)
OS: Ubuntu 14.04
Java: 1.8.0_45-b14 on the master, 1.8.0_101-b13 on the slaves (affected builds use 1.7.0_80 installed as a tool by Jenkins)
I have recently started using the Amazon EC2 plugin to bring up Jenkins build slaves on demand. They are all created from the same AMI and set to shut down instead of terminate. The transition went very smoothly (as soon as the AMI had everything that was needed) however two of our builds are now misbehaving every single time. I've been able to find some very old slightly similar issues in Jira and Stackoverflow but nothing identical (and nothing using recent version of Jenkins). I am not 100% convinced the EC2 plugin has anything to do with this however this is when the problem started exhibiting.
I've managed to narrow this issue to the 'Clean up unused Subversion modules' option in 'Build environment'. Whenever the build starts (either by SCM poll trigger or manually triggerred), the SCM checkout happens successfully (this is regardless of there being changes) and after the 'At revision xxx' message is printed out in the log, nothing happens anymore (no matter how long the job is left running) apart from the spinning circle. I have discovered that hitting the cancel button when in the console log page (top right next to the progress bar) will display a stacktrace in the build but the build will continue happily afterwards. Here's the stacktrace:
I've worked around this by disabling this option. Let me know if I can provide any more info that could help.