We have 50 projects in a monorepo and we use multibranch-build-strategy-extension-plugin to trigger the correct builds based on commit contents.

It does not work with initial (branch indexing) builds. For example, every time a new merge request is created, all of those 50 MR builds get unnecessarily triggered, no matter what is configured in the plugin strategies. Total waste of build resources.

What I assume is happening is that the "previous" commit hash that it tries to compare against (to see changed files) is not yet set during the very first build. So the first build would need to be treated somehow differently for the plugin to see the changes between the MR commit hash and the MR's parent commit hash.

Not sure if that can be fully done within the multibranch-build-strategy-extension-plugin, or does it need changes elsewhere.