You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Jenkins 2.452.3
ignore-committer-strategy 1.0.4
cloudbees-bitbucket-branch-source 887 or 888 likewise, 886 worked ok
What Operating System are you using (both controller, and any agents involved in the problem)?
Rocky Linux 9
Reproduction steps
add at least 2 commits by the same exempted author and push them at the end of the build.
--- or ---
just trigger a multibranch pipeline scan.
Expected Results
There should be no difference regarding the number of commits; if the push only contains commits of the same exempted author, the build should not be triggered.
Actual Results
With builds that produce 2 commits by our CI user, those get endlessly re-triggered by branch events.
With builds that only produce 1 commit, the strategy works as expected.
When triggered by a scan, ALL branches get rebuilt
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered:
Jenkins and plugins versions report
Environment
What Operating System are you using (both controller, and any agents involved in the problem)?
Rocky Linux 9
Reproduction steps
add at least 2 commits by the same exempted author and push them at the end of the build.
--- or ---
just trigger a multibranch pipeline scan.
Expected Results
There should be no difference regarding the number of commits; if the push only contains commits of the same exempted author, the build should not be triggered.
Actual Results
With builds that produce 2 commits by our CI user, those get endlessly re-triggered by branch events.
With builds that only produce 1 commit, the strategy works as expected.
When triggered by a scan, ALL branches get rebuilt
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: