Re: Pipeline & GH pull requests

In case anyone else is playing along (or for future me), I fixed the first problem by specifying "master" instead of "*" for branches to build: [image: Inline images 1] It noticed force pushes after that too. And I discovered that the plugin was listening

Re: Pipeline & GH pull requests

Also, is there any way to prevent multiple pipeline builds for the same branch (e.g. master) running concurrently? That was opt-in, in the old world. [image: Inline images 1] On 29 September 2016 at 15:44, Graham Hay wrote: > Is there any way to get the id of a pull request, in the brave new >

Re: Pipeline & GH pull requests

I'm still having trouble with this (not since Oct, obviously, I took a break). When I push a new (feature) branch, it immediately starts building: because I have "Build origin branches" ticked (I assume I need that to get master to build?). That build fails, because it's expecting the branch na

Re: Pipeline & GH pull requests

The answer was to tick this box: [image: Inline images 1] under Project Sources -> Repository Sources -> GitHub Org -> Advanced in the folder configuration. I then got PR builds, with a branch named as "PR-${prNumber}". I think the fork PR version was ticked by default, but that's not our workflow

Pipeline & GH pull requests

Is there any way to get the id of a pull request, in the brave new pipeline world? It was exposed as $ghprbPullId when using the GHPRB plugin. I'm using a GH Org Folder & Multibranch, with a Jenkinsfile. Also, what do I have to do to get something to appear in