That refspec seems to be mentioned in the Stash pull request builder plugin
documentation. You might dig deeper there.
https://wiki.jenkins-ci.org/display/JENKINS/Stash+pullrequest+builder+plugin#Stashpullrequestbuilderplugin-BuildingthemergeofSourceBranchintoTargetBranch
Mark Waite
On Thu, Jul
Problem solved more-or-less.
The Git plugin was configured with
+refs/pull-requests/*/from:refs/remotes/origin/pull-requests/*/from.
I removed this configuration and no longer have the extra branches.
I'm unable to find any documentation that describes this refspec. It
appears to be somethi
Also, if I log directly into Stash and cd to the repository, the git branch
command does NOT show any of these phantom origin/pull-requests branches.
These seem to be something being fabricated by Jenikins.
On Wednesday, July 13, 2016 at 9:01:30 AM UTC-7, Michael Giroux wrote:
>
> BTW, when I
BTW, when I clone the repository to my local workstation, the
origin/pull-requests/* branches do NOT appear in "git branch -a". However,
when I log into the Jenkins server, and cd to the job directory, the
pull-request branches DO appear, so Git plugin is using something special
to cause the b
This question involves Git plugin, Stash, and SonarQube integration, so
there are multiple bits that we need to coordinate.
1. We are using Stash with the Jenkins Web Hook to trigger builds when
developers push code to a branch.
2. The build checks the code out to a local branch using
