Jumping in late. But can you explain what is mean't by a PR-merge branch?
I googled to find nothing specific to defining what a PR-merge branch is?
Is this a Jenkins specific lingo or Git lingo?
On Saturday, 5 August 2017 10:05:35 UTC-7, Stephen Connolly wrote:
>
>
> On Sat 5 Aug 2017 at 18:00, B
On Sat 5 Aug 2017 at 18:00, Budding Mechanic
wrote:
> So if Jenkins is restarted and scheduleBuild(0) is called during startup,
> the scan will occur for the org and all builds will start.
>
> But technically, the only branches that will actually build are the ones
> in which the SHA changed sinc
So if Jenkins is restarted and scheduleBuild(0) is called during startup,
the scan will occur for the org and all builds will start.
But technically, the only branches that will actually build are the ones in
which the SHA changed since the last successful build? eg. while Jenkins
was down, a
`scheduleBuild(0)` on the multibranch project is the api for scanning now
(as a build of a multibranch project is a scan)
On 5 August 2017 at 04:57, Stephen Connolly wrote:
> Scan repository now will always kick off builds of branches that have
> changes since the last scan where those changes w
Scan repository now will always kick off builds of branches that have
changes since the last scan where those changes were missed by the event
handler... so you are kind of asking for the non-possible
On 4 August 2017 at 06:13, Budding Mechanic
wrote:
> Hi,
>
> I'm using the multibranch pipeline
