I'm able to reproduce the error with my test job if I have it restricted to the same slave that the problem job is using. It happens with the single SCM job that has multiple branches, but I haven't been able to reproduce with just a single branch configurations, so I'm thinking it has to do with a particular version of Git and the multiple branch issue (or single branches always run on master so I don't see it). The slave in question is running 1.7.9.5 which meets the requirement, but not the recommended version of 1.8.
I don't feel like upgrading that slave right now, but I can at least limit the job to other slaves to see if that works around the problem. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20db5c14-70c1-4c27-b0b2-200c274b291d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
