Skip to content
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

Fix so 'Never rebuild merge requests' feature works #869

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

Osmyslitelny
Copy link

@Osmyslitelny Osmyslitelny commented Dec 10, 2018

I started from this issues #705. The main problem was we get 'update' action not only when State is updated but when State is open (you open MR and add some fix push). After that I found that my closed MR doesn't trigger job. After investigation I got that hook was with Action close, not closed. I think It isn't all problem and issues from this scope (MR and webhooks). But it's more popular cases and I think in the future we should to verify what is State and what is Action, and which rule should compare them.

Fixes #705.

State - closed, Action - close
we set it on 1st place because the more important type of hook than flag approved or not.
Also update action often came with opened state.
@Osmyslitelny Osmyslitelny changed the title Fix/merge request hooks behavior merge request hooks behavior (close, closed, never) Dec 11, 2018
@omehegan
Copy link
Member

@Osmyslitelny thanks a lot for working on this! I will build a snapshot and post the link to it in #705 so other folks can try it out.

@omehegan omehegan changed the title merge request hooks behavior (close, closed, never) Fix so 'Never rebuild merge requests' feature works Dec 17, 2018
@mattiasb
Copy link

Any chance this could get in soonish? :)

@omehegan omehegan closed this Oct 30, 2019
@omehegan omehegan reopened this Oct 30, 2019
@omehegan
Copy link
Member

Trying to trigger the CI again but no luck.

@markyjackson-taulia in #705 I published a snapshot with this fix and folks confirmed that it resolved the issue, so we can probably merge it. Would be nice to get the CI to pass though.

@omehegan
Copy link
Member

Test passing now :D

@fmdaboville
Copy link

Is this will be merged and release soon ? Thanks

@zottinor
Copy link

zottinor commented Apr 3, 2020

Hi dears, what is the progress on this issue

@markjacksonfishing
Copy link
Contributor

Someone needs to have the build pass ci. Cannot merge until that happens

@Osmyslitelny
Copy link
Author

Osmyslitelny commented Apr 13, 2020

@omehegan If I get it right, MR haven't problem with CI (сш-fail https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgitlab-plugin/detail/PR-869/31/pipeline connect with master - https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fgitlab-plugin/detail/master/195/pipeline , not with current MR) . And there #869 (comment) you said "all right". Are you going to merge it soon? It would me nice. Because it isn't very comfortable keep custom-snapshot-fork into project-jenkins. Different issues with versions and etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The "Never" option for "Rebuild open Merge Requests" does not prevent a build
7 participants