Mark Waite commented on Bug JENKINS-26290

I've seen that message infrequently myself. If you're willing to insert some debugging code into the git plugin and deploy it into your environment where the random failure happens, it could provide deeper understand of the problem.

What I'd suggest (without having written the code):

  • Insert additional debug code into the GitException which only executes if the stderr of the exception includes the message "reference is not a tree"
  • In that additional debug code, run "git show <SHA1-in-the-error>"
  • In that additional debug code, run "git ls-remote origin <SHA1-in-the-error>"

I think the intermittent nature of the problem means that you'll need to insert the debug code into your production instance, or you'll need to configure another instance which shows the problem.

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.

Reply via email to