How to use the plugin: Pipeline: Multibranch build strategy extension

I’m using the plugin: “Pipeline: Multibranch build strategy extension” with a multibranch pipeline (declarative).

From the jenkins logs I can see it says (correctly) that it will skip the build.

2024-01-10 04:54:26.949+0000 [id=1716]	INFO	h.triggers.SCMTrigger$Runner#run: SCM changes detected in ... » develop. Triggering  #403
2024-01-10 04:54:32.944+0000 [id=3396]	INFO	c.i.j.p.m.b.ExcludeRegionBranchBuildStrategy#shouldRunBuild: All changes matching excluded regions, skipping build

Nevertheless the build does not get skipped.
Has anyone got this plugin to work?

Jenkins setup:
Jenkins: 2.426.2
OS: Linux - 4.15.0-135-generic
Java: 11.0.19 - Ubuntu (OpenJDK 64-Bit Server VM)

ace-editor:1.1
analysis-model-api:11.14.0
ansicolor:1.0.4
ant:497.v94e7d9fffa_b_9
antisamy-markup-formatter:162.v0e6ec0fcfcf6
apache-httpcomponents-client-4-api:4.5.14-208.v438351942757
authentication-tokens:1.4
blueocean:1.24.4
blueocean-autofavorite:1.2.4
blueocean-bitbucket-pipeline:1.24.4
blueocean-commons:1.27.9
blueocean-config:1.27.9
blueocean-core-js:1.27.9
blueocean-dashboard:1.27.9
blueocean-display-url:2.4.2
blueocean-events:1.24.4
blueocean-git-pipeline:1.24.4
blueocean-github-pipeline:1.24.4
blueocean-i18n:1.27.9
blueocean-jira:1.24.4
blueocean-jwt:1.27.9
blueocean-personalization:1.27.9
blueocean-pipeline-api-impl:1.24.4
blueocean-pipeline-editor:1.24.4
blueocean-pipeline-scm-api:1.24.4
blueocean-rest:1.27.9
blueocean-rest-impl:1.24.4
blueocean-web:1.27.9
bootstrap4-api:4.6.0-6
bootstrap5-api:5.3.2-3
bouncycastle-api:2.30.1.77-225.v26ea_c9455fd9
branch-api:2.1144.v1425d1c3d5a_7
build-timeout:1.32
build-token-root:151.va_e52fe3215fc
bulk-builder:1.5
caffeine-api:3.1.8-133.v17b_1ff2e0599
checks-api:2.0.2
cloudbees-bitbucket-branch-source:2.9.7
cloudbees-folder:6.858.v898218f3609d
command-launcher:107.v773860566e2e
commons-lang3-api:3.13.0-62.v7d18e55f51e2
commons-text-api:1.11.0-95.v22a_d30ee5d36
conditional-buildstep:1.4.3
config-file-provider:959.vcff671a_4518b_
configurationslicing:1.52
credentials:1311.vcf0a_900b_37c2
credentials-binding:642.v737c34dea_6c2
data-tables-api:1.13.8-2
display-url-api:2.200.vb_9327d658781
docker-commons:1.17
docker-workflow:1.26
dtkit-api:3.0.2
durable-task:543.v262f6a_803410
echarts-api:5.4.3-2
email-ext:2.103
envinject:2.908.v66a_774b_31d93
envinject-api:1.199.v3ce31253ed13
external-monitor-job:215.v2e88e894db_f8
favorite:2.208.v91d65b_7792a_c
font-awesome-api:6.5.1-1
forensics-api:2.3.0
git:5.2.1
git-client:4.6.0
git-server:1.9
github:1.33.1
github-api:1.318-461.v7a_c09c9fa_d63
github-branch-source:2.9.7
gradle:2.9
gson-api:2.10.1-15.v0d99f670e0a_7
handlebars:3.0.8
handy-uri-templates-2-api:2.1.8-30.v7e777411b_148
html5-notifier-plugin:1.5
htmlpublisher:1.32
instance-identity:185.v303dc7c645f9
ionicons-api:56.v1b_1c8c49374e
jackson2-api:2.16.1-373.ve709c6871598
jakarta-activation-api:2.0.1-3
jakarta-mail-api:2.0.1-3
javadoc:243.vb_b_503b_b_45537
javax-activation-api:1.2.0-6
javax-mail-api:1.6.2-9
jaxb:2.3.9-1
jdk-tool:73.vddf737284550
jenkins-design-language:1.27.9
jira:3.2
jjwt-api:0.11.5-77.v646c772fddb_0
job-parameter-summary:0.5
joda-time-api:2.12.5-5.v5495a_235fedf
join:1.21
jquery:1.12.4-1
jquery-detached:1.2.1
jquery3-api:3.7.1-1
jsch:0.2.16-86.v42e010d9484b_
json-path-api:2.8.0-21.v8b_7dc8b_1037b_
junit:1252.vfc2e5efa_294f
ldap:711.vb_d1a_491714dc
lockable-resources:1224.v5e9500f98269
log-parser:2.3.3
mailer:463.vedf8358e006b_
mapdb-api:1.0.9-28.vf251ce40855d
matrix-auth:3.1.8
matrix-project:822.v01b_8c85d16d2
maven-plugin:3.23
mercurial:2.12
mina-sshd-api-common:2.11.0-86.v836f585d47fa_
mina-sshd-api-core:2.11.0-86.v836f585d47fa_
momentjs:1.1.1
multibranch-build-strategy-extension:46.v9de263eb_869c
naginator:1.436.vb_e769dcb_cdf6
nested-view:1.33
okhttp-api:4.11.0-157.v6852a_a_fa_ec11
pam-auth:1.10
parameterized-trigger:787.v665fcf2a_830b_
pipeline-build-step:540.vb_e8849e1a_b_d8
pipeline-graph-analysis:1.10
pipeline-input-step:2.12
pipeline-milestone-step:111.v449306f708b_7
pipeline-model-api:2.2168.vf921b_4e72c73
pipeline-model-definition:1.8.4
pipeline-model-extensions:1.8.4
pipeline-multibranch-defaults:2.1
pipeline-rest-api:2.19
pipeline-stage-step:305.ve96d0205c1c6
pipeline-stage-tags-metadata:2.2168.vf921b_4e72c73
pipeline-stage-view:2.19
pipeline-utility-steps:2.16.0
plain-credentials:143.v1b_df8b_d3b_e48
plugin-util-api:3.8.0
popper-api:1.16.1-3
postbuild-task:1.9
pubsub-light:1.18
purge-build-queue-plugin:88.v23b_97b_f2c7a_d
purge-job-history:1.6
run-condition:1.7
saferestart:0.7
scm-api:683.vb_16722fb_b_80b_
script-security:1313.v7a_6067dc7087
simple-theme-plugin:176.v39740c03a_a_f5
snakeyaml-api:2.2-111.vc6598e30cc65
sse-gateway:1.26
ssh-credentials:308.ve4497b_ccd8f4
ssh-slaves:1.31.5
ssh-steps:2.0.68.va_d21a_12a_6476
sshd:3.312.v1c601b_c83b_0e
structs:325.vcb_307d2a_2782
subversion:2.17.3
swarm:3.44
template-project:1.5.2
throttle-concurrents:2.14
timestamper:1.26
token-macro:400.v35420b_922dcb_
trilead-api:2.133.vfb_8a_7b_9c5dd1
variant:60.v7290fc0eb_b_cd
warnings-ng:8.10.1
windows-slaves:1.8.1
workflow-aggregator:2.6
workflow-api:1283.v99c10937efcb_
workflow-basic-steps:1042.ve7b_140c4a_e0c
workflow-cps:3837.v305192405b_c0
workflow-cps-global-lib:2.18
workflow-durable-task-step:1313.vcb_970b_d2a_fb_3
workflow-job:1385.vb_58b_86ea_fff1
workflow-multibranch:770.v1a_d0708dd1f6
workflow-scm-step:415.v434365564324
workflow-step-api:639.v6eca_cd8c04a_a_
workflow-support:865.v43e78cc44e0d
xunit:3.1.3

Hi @JonnyWylie and welcome to this community. :wave:

The issue you’re facing could be due to a few reasons, here a the ones I’m thinking of:

  • There might be a conflict with another plugin or configuration that’s causing the build to proceed despite the exclusion rule. Check your other plugins and configurations to see if there’s anything that might be overriding the build strategy.
  • The exclusion rule might not be correctly configured. Make sure that the rule is correctly set up to match the changes you want to exclude.
  • There might be a bug in the plugin itself. If you’ve checked the above and everything seems to be in order, it might be worth reporting the issue to the plugin maintainers.

The exclusion rule is definitely correctly configured, because I can see in the Jenkins logs, it says that the build will be skipped, but it proceeds anyway.

I’m using it in conjunction with the Filter by name (with wildcards) behaviour, because I don’t want it to run for every branch.
Could that be overriding it?

1 Like