|
||||||||
|
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 Heather, no worries - late replying myself![]()
.
I've seen it happen to a handful of different people, including myself. My workspace is public (as we encourage all of our team to do) so visibility shouldn't be an issue. We only have a couple of components that rarely change so I imagine it's unlikely any of the hanging builds had something different, component-wise.
The load directory for the build definition is set to 'src' so that it checks out to {JOB_WORKSPACE}/src.
There are no special actions checked nor any excludes set for the load actions or accept options. I guess these are default values but I can send you exactly what option has what value if you need (assuming some might not be blank by default).
There haven't been many personal builds lately so I unfortunately don't have the output log to hand. Next time I see a hanging build, I will update this ticket.
Not quite sure what you mean by the build result having an activity for fetching files but the build doesn't get to the point of actually building anything. It tries to checkout the src code and never comes back from there.
Trying to abort the build via Jenkins has no effect. The only way to stop it is to kill the master Jenkins process.
Hope that helps, let me know if you need anything else!
Thanks,
James