How to collect all merge requests with a tag in jenkins?

Question

Jenkins

I want to make an image for a test circuit gather.
The order I see is this:
1) In jenkins, we collect all merge requests for a specific tag (for example, deploy_test_label)
2) We merge all branches from MP into one (for example, deploy_test_branch)
3)

We run tests using this code, we collect an image there are some ideas
1) In jenkins, in the build section, we pull the gitlab API Gitlab API for MP
2) We parse the answer there, get the branches and do git merge,

But I don’t quite understand how to implement this.
Plus, has anyone done this before me? Used Google. but maybe wrong)

Answer 1

In principle, this cannot be done in the concept of ci, all processes are launched either when an MR appears or when it is approved. If there is more than one open MR in the turnip - it's time to run to sound the alarm

Answer 2

Wrong approach.
If this is a merge request to the same release, then things that are unrelated to each other should not cause any conflicts in testing.
If they do arise, they should be sawn into the same feature branch.
What you are trying to fix are integration testing bugs. It is corny corrected by the fact that the one who sent his merge request second and caught the bug will sort it out.
It’s just that in practice, such a situation is extremely rare with a normal application architecture, and therefore changing the entire CI process for the sake of this particular feature and contrary to the normal git-flow for features is wrong.