I have a multi-branch pipeline project which pulls from two separate repositories; a release repository, and a development repository. The release repository is only updated on product release, and contains build files and artifacts which are packaged up and pushed to deployment.

In this multi-branch pipeline, if there are changes on the development repository, it triggers builds on every branch–including those in the release repository.

I don't want Jenkins to try and repeatedly deploy packages that haven't changed just because a developer makes a commit to the development repo. Shouldn't each scanned sub-project within the multi-branch pipeline only build when its repository has SCM changes?