-
Notifications
You must be signed in to change notification settings - Fork 618
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed Merge Request Events does not trigger job #948
Comments
Have you checked the Jenkins log for the Gitlab plugin, in Jenkins > System Log > Gitlab plugin? |
Experiencing the same issue here, and the log in Jenkins is the same as @dsiragusa provided, i.e. no further log after MergeRequestBuildAction. This feels like the logic did not go beyond the |
In addition to the above observation, should the |
Still an issue 2 years later. Are there no plans for this to be fixed? |
I am having the same issue. |
Same issue here.. |
Can confirm that Approved Merge Requests (EE-only) works to allow closed events to trigger (unintuitively). Unfortunately, this also makes "Approve" events trigger the job (but not revoking Approval for some reason), and this is undesirable. And while the plugin does know the state change because GitLab sends it in the webhook, the plugin does not expose it to the pipeline in any variable. Thus, a job triggered by an Approval looks identical to a job triggered by the MR being (re)opened, or a new commit being pushed, etc. Would prefer a way to trigger the job on closed/merged events without also triggering on Approval, but even if we wanted to check this in the job itself, there's no way to determine that the job was triggered by an approval vs. another event. Additionally, the |
Issue
Context
Logs & Traces
Problem description
Hello, I'd like to trigger a job on Accepted Merge Request Events and Closed Merge Request Events.
Accepted Merge Request Events correctly trigger the job but that's not the case for Closed Merge Request Events:
the webhook is correctly sent by Gitlab, Jenkins answers with a 200 status code but does nothing.
The text was updated successfully, but these errors were encountered: