It would definitely be my preferred way of building code, but unfortunately the Jenkins master has to clone and perform the merge per pipeline every time. That doesn't scale on a sizeable repo with many active PRs and 12 multibranch pipelines :(
I've seen people merge PRs with an old base before and break things because they assumed that when their "Current pull request revision" build passes everything is fine. -- 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/d61b5137-38c0-4b2e-8eaa-25cb32ff33ff%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
