As is pretty well documented in JENKINS-37491, when one has many PRs open on a given GitHub project/repo and a new commit lands to the base branch of all of those PRs (I'm looking at you master), all of the open PRs get a build scheduled.

This can bring a Jenkins server to it's knees.

I don't think we need to rehash the debate about whether every PR should be built against current master to ensure it doesn't break the new master.  That can be enforced with branch protection in GitHub if that's something people want to do.

But having your Jenkins server crush and take days to flush out when a new commit lands to master is just unworkable.

JENKINS-37491 proposed:

• Install Basic Branch Build Strategies plugin and add the "Change Requests" with "Ignore rebuilding merge branches when only the target branch changed" selected to your build strategies

but that doesn't seem to be applicable to GitHub organisation jobs.

So what is the solution here?

I'm using Pipeline: Multibranch jobs if that matters.