Is there an alternative to a full checkout on the master to determine the merge result of a Jenkinsfile for PR merge builds in a multibranch project? Specifically using github. I'm finding the full checkout seems to strain the whole system when the master needs to check out a large repo ~15 times at once for my build. I understand the need for this behaviour as a default and that mine is an edge case.
Does github store the merge result in a hidden branch that can be leveraged? Or can Jenkins / the git plugin suites do some kind of double lightweight checkout trickery? Will have to switch to pr-head building for now :( -- 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/53442155-9a4b-498d-9ffa-8d90a36e33dc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
