Thanks, yes it makes sense now that I have seen it trigger PR rebuilds when master changes. This was surprising at first, but makes sense if you are to assume that validated against a merge with master means it is always safe to merge.
On Wednesday, July 13, 2016 at 1:44:21 PM UTC+10, Jesse Glick wrote: > > On Tue, Jul 12, 2016 at 5:45 AM, Michael Neale <mne...@cloudbees.com > <javascript:>> wrote: > > The behavior I am seeing is that when there is an origin PR opened, it > kicks off 2 builds, one for the PR and one for the branch > > Well that is what you requested—to build it both ways. > > > even if there is no merge needed with master > > Whether or not a merge is needed may change from build to build. Try > committing something to `master`. You should see a second build of the > PR job. > > > I can't quite fathom what the help text says > > PRs welcome. > > BTW I did update the formal documentation to make mention of the new > options. But whoever is responsible for publishing these updates has > so far not done so. Perhaps you can help nudge them. When a > documentation person has the time, this documentation ought to get > moved to jenkins.io, or whatever the preferred home for plugin > documentation is these days (it seems to be in flux). > > > What I would like is for branch to be built, but only an additional > build performed IF it actually isn't up to date with master. Is this > possible at the moment or not? > > Not as such. Again, the checkboxes just control which *jobs* are > defined according to inherent aspects of the branches/PRs. The need > for, and validity of, a merge is liable to vary from one commit to the > next after the job has been created. > > > Perhaps another option is to not build branches, but only build PRs, > then it would only show up once? > > Sure, just uncheck “Build origin branches also filed as PRs”. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1b7781f5-9365-4213-9a6b-aa68e7fdc050%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
