James, Nord - thank you! For my pipeline scaling is not an issue, but merging strategy is breaking SonarSource orchestration. I think "The current pull request revision" will be nice as far as I'll add a check that branch was updated from the master into pipeline itself.
On Thursday, February 14, 2019 at 6:58:17 AM UTC+2, Vitaly Karasik wrote: > > GitHub Branch Source Plugin uses "Merging the pull request with the > current target branch revision" strategy by default for "Discover pull > request". > What are the reasons for using it and not "The current pull request > revision"? > > TIA, > Vitaly > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/782aa3dd-8680-433d-9963-8882cca8e323%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
