[JIRA] (JENKINS-36563) Git plugin does not fetch branch to merge to when merge before build is used

[mark.earl.wa...@gmail.com (JIRA)]

Title: Message Title

Mark Waite commented on JENKINS-36563   Re: Git plugin does not fetch branch to merge to when merge before build is used In one of the failing repositories, could you run the command git branch -a? It will probably show that there is no branch named remotes/origin/master. In one of the failing repositories, could you run the command git config --get remote.origin.fetch? It may show that the refspec is something other than the default (though I don't see anything in your pipeline definition which would indicate you're using a non-default refspec). The default refspec is +refs/heads/*:refs/remotes/origin/* Those questions are all attempting to detect if the failure to parse the origin/master reference is a side effect of the fix for JENKINS-31393 which was introduced in 2.5.1. If you are able to roll-back your git plugin to 2.5.0 and wipe the workspace for those builds, that may tell us if that is the cause. Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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.