Gitlab defines pipelines per commit and not per MR when using a webhook to Jenkins
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=248559)
</details>
<!--IssueSummary end-->
We would like Jenkins pipelines will be triggered by webhook not per commit but per MR.
The reason for that are:
1. Using gitlab-ci it doesn't have this behavior.
When looking into Gitlab's API you can see that there is a way to update a commit status to a specific pipeline.
https://docs.gitlab.com/ee/api/commits.html#post-the-build-status-to-a-commit
they even explain there:
**pipeline_id integer no The ID of the pipeline to set status. Use in case of several pipeline on same SHA.**
2. The reason why we need it is because we have diffrent tests running according to the target branch.
issue