Web hook fired on Merge Request does not contain repo url about jenkins-gitlab-hook-plugin HOT 5 CLOSED

I suspect that Gitlab sends a bit different payload when merge request is in question, as opposed to payload for a regular commit. Can you provide the exact payload?

from jenkins-gitlab-hook-plugin.

According to the api that's correct. This is what GitLab sends (also in line with what I receive as payload).

Merge request events

Triggered when a new merge request is created or an existing merge request was updated/merged/closed.

Request body:

{
  "object_kind": "merge_request",
  "object_attributes": {
    "id": 99,
    "target_branch": "master",
    "source_branch": "ms-viewport",
    "source_project_id": 14,
    "author_id": 51,
    "assignee_id": 6,
    "title": "MS-Viewport",
    "created_at": "2013-12-03T17:23:34Z",
    "updated_at": "2013-12-03T17:23:34Z",
    "st_commits": null,
    "st_diffs": null,
    "milestone_id": null,
    "state": "opened",
    "merge_status": "unchecked",
    "target_project_id": 14,
    "iid": 1,
    "description": ""
  }
}

from jenkins-gitlab-hook-plugin.

OK, so that explains it.
See https://github.com/elvanja/jenkins-gitlab-hook-plugin#hook-data-related, I added an example of Gitlab payload for a commit. You can see that that payload contains data I can use to determine which project is to be built.

One question though. Before merge request, a commit to feature branch was surely made. And that has undergone a Jenkins build, if all is set correctly. Why would you need to build again for merge request?

from jenkins-gitlab-hook-plugin.

Yes, thanks. So basically the plugin supports only push events now, as there's no trivial way to get the url. That would require reading e.g. a project configuration parameter, as the repo url is configured there (git plugin).

About your question: This job needs quite some time to build so I don't want to trigger it with every commit to a feature branch. Much rather after a MR is opened. The other relevant plugin (Gitlab Merge Request Builder) does that I think, but uses polling.

Anyway, thanks for the reply. If you have a good suggestion, I'm more than happy to hear it :-)

cheers

from jenkins-gitlab-hook-plugin.

Well, I guess that since it's done in mentioned plugin, it is doable. Please try the other plugin, no sense in duplicating behavior if it works :-) Other than that, no suggestions, sorry!

from jenkins-gitlab-hook-plugin.