I would like to ask for a feature that would help a lot in the following scenario:

• we use git to promote all kind of stuff from environment to environment (some might call it GitOps or therelike)
• we configure/ setup jenkins fully automated and spinn up new env when ever we need to change the configuration
• we use 'cloudbees-bitbucket-branch-source' to monitor/ build most of our builds

Now, when we spawn a new jenkins environment (because of some config changes), then 'cloudbees-bitbucket-branch-source' triggers a new initial build of all the 'master' branches too. This is a problem, as this will now cause new (unwanted) releases of some of our artifacts or even trigger an installation of the apps in a environment which is not required (because there was no actual change on the 'master' branch).

What I'm asking for, is some kind of way stop some branches being automatically triggered after the scan of the organization folder.

I know there are options to include/ exclude branches (even with regex), but thats not what I'm looking for - as far as I know, all the existing filters and options are to permanently exclude the branch from being build. But what we need is to be able to ensure that some branch gets only build when there is an actual change, but not when the branch was discovered during organization folder scanning.