[JIRA] (JENKINS-58178) Git Plugin fails to mergeBeforeBuild with "ambiguous argument"

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

Title: Message Title

Mark Waite commented on JENKINS-58178   Re: Git Plugin fails to mergeBeforeBuild with "ambiguous argument" Merge is best done through the branch source plugins (GitHub, Bitbucket, and Gitea) rather than through the git plugin. The branch source plugins provide options to evaluate pull requests and they provide the necessary configuration to support the evaluation of pull requests. If your environment won't allow you to use one of those branch source plugins, then the refspec used in the checkout needs to be extended to include the branch that is being merged in addition to the branch that is being built. Your example log lists: > git fetch --no-tags --progress https://github.com/sample/myrepo.git +refs/heads/update_pipeline:refs/remotes/origin/update_pipeline # timeout=10 That statement uses a narrow refspec that pulls only the branch being built ( update_pipeline ) and no other branches. That reduces the impact of the CI job on the remote server by requesting only the data needed for that specific branch. It also means that other branches are not available in the workspace repository. You'll need to either use the GitHub branch source plugin (preferred) or adjust the remote config that is currently listed as: userRemoteConfigs: scm.userRemoteConfigs Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200229.1561448635000.8007.1561461840171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.