-
Bug
-
Resolution: Unresolved
-
Major
-
None
Hi,
My impression is that this plugin is non-functional, at least when used with the pollSCM trigger. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed my/dir/**
Yet when changes are made outside my/dir/** a build is triggered.
The regions directory patterns don't seem to be evaluated. My job is triggered and logs show:
j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering
If this was working, when I commit the irrelevant file, I would expect to see eg log message:
c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build
But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Nothing except INFO level messages are logged at build time.
Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. Any file change wrongly triggers, when none should.
Using latest LTS Jenkins (v2.462.1) and latest multibranch-build-strategy plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin?
BTW, I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs, and I'm setting a unique ID for each of my jobs. No dice.
Thanks.
[JENKINS-73598] Does multibranch-build-strategy-extension plugin work at all?
Brendan Holmes
created issue -
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering If this was working, when I commit the irrelevant file, I would expect to see eg log message: c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build But this is not logged. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: _j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering_ If this was working, when I commit the irrelevant file, I would expect to see eg log message: _c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build_ But this is not logged. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: _j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering_ If this was working, when I commit the irrelevant file, I would expect to see eg log message: _c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build_ But this is not logged. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is not logged. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is not logged. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I set options, not at build time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I set options, not at build time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
Brendan Holmes
made changes -
| Summary | Original: Does this plugin work at all? | New: Does multibranch-build-strategy plugin work at all? |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? |
New:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs. I'm setting a unique ID for each of my jobs. No dice. |
Brendan Holmes
made changes -
| Description |
Original:
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/**
Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs. I'm setting a unique ID for each of my jobs. No dice. |
New:
Hi,
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/** Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs. I'm setting a unique ID for each of my jobs. No dice. Thanks. |
Brendan Holmes
made changes -
| Description |
Original:
Hi,
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed /my/dir/** Yet when changes are made outside /my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs. I'm setting a unique ID for each of my jobs. No dice. Thanks. |
New:
Hi,
My impression is that this plugin is non-functional. None of the options for triggering builds only when files in a particular directory are changed, or suppressing builds when files in excluded dirs are changed appear to work. Eg in my job, I've set Branch Sources --> Property strategy --> Build Strategies --> Accept build by included regions strategy --> in the "Trigger builds for included regions" text box, I've typed my/dir/** Yet when changes are made outside my/dir/** a build is triggered. Same occurs if I type "**" in Cancel build by excluded regions strategy --> Don't trigger build for excluded regions, which should avoid triggering ANY builds. The regions directory patterns don't seem to be evaluated. My job is triggered and logs show: {code:java} j.scm.impl.SCMTriggerListener#onSCMHeadEvent: Triggering polling of myjob/my-branch h.triggers.SCMTrigger$Runner#run: SCM changes detected in myjob >> my-branch. Triggering {code} If this was working, when I commit the irrelevant file, I would expect to see eg log message: {code:java} c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#shouldRunBuild: No matching any included regions, skipping build {code} But this is only logged when I configure my job, not at build time. Nor are there any other logs containing "BuildStrategy" at build-time. Using latest LTS Jenkins (v2.462.1) and latest plugin (v51.v88f14e2a_4075). Is anyone successfully using this plugin? I've followed a couple of tips in issues about this plugin, such as ignoring builds triggered by indexing using "suppress automatic SCM triggering" in my jobs. I'm setting a unique ID for each of my jobs. No dice. Thanks. |