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
What Operating System are you using (both controller, and any agents involved in the problem)?
Our controller is currently running in Docker, and we're running the following image - eclipse-temurin:17.0.9_9-jre-alpine https://hub.docker.com/_/eclipse-temurin
Reproduction steps
We curently have 2 pipelines configured for our Gitlab project, phase 1 and phase 2.
Phase 1 is configured to trigger with the following settings -
The issue we are facing is that Phase 2 is also being triggered on merge request open, this shouldn't be happening as it should only be triggering when a comment on the MR matches the noteRegex, or the MR is merged.
FYI we only noticed this after upgrading the Gitlab plugin from 1.6.0, this was working fine and we had it pinned to 1.6.0 but we've been forced to update to 1.8.0.
Thanks.
Expected Results
Phase 2 should only trigger when an MR is merged, or we match the comment regex.
Actual Results
Phase 2 kicks off when we open an MR, similar to Phase 1.
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)?
Our controller is currently running in Docker, and we're running the following image -
eclipse-temurin:17.0.9_9-jre-alpine
https://hub.docker.com/_/eclipse-temurin
Reproduction steps
We curently have 2 pipelines configured for our Gitlab project, phase 1 and phase 2.
Phase 1 is configured to trigger with the following settings -
Phase 2 is configured to trigger with the following settings -
The issue we are facing is that Phase 2 is also being triggered on merge request open, this shouldn't be happening as it should only be triggering when a comment on the MR matches the
noteRegex
, or the MR is merged.FYI we only noticed this after upgrading the Gitlab plugin from
1.6.0
, this was working fine and we had it pinned to1.6.0
but we've been forced to update to1.8.0
.Thanks.
Expected Results
Phase 2 should only trigger when an MR is merged, or we match the comment regex.
Actual Results
Phase 2 kicks off when we open an MR, similar to Phase 1.
Anything else?
No response
Are you interested in contributing a fix?
No response
The text was updated successfully, but these errors were encountered: