the main reason for using it is you want to check that the result of a PR if merged would result in working code. a PR can be based on any code even 1 year old, so this strategy makes sure it is up to date before building and testing.
On Thu, 14 Feb 2019, 05:58 Vitaly Karasik <[email protected] 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/3211ba6a-cc5f-44a2-acd8-d0fd31e4716c%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/3211ba6a-cc5f-44a2-acd8-d0fd31e4716c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAPzq3pfzVQfVOE9NsZiKszBP-H9Xw9p7z3V7-pciCeDBBQn%3D%3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
