How can I pass my merge request’s target branch into a trigger pipeline in GitLab CI?

How can I pass my merge request’s target branch into a trigger pipeline in GitLab CI?

How can I pass my merge request’s target branch into a trigger pipeline in GitLab CI?

How can I pass my merge request’s target branch into a trigger pipeline in GitLab CI?

In the CI/CD Pipeline, I want to indicate for different gitlab-runner to run the job when the source branch is being merged to target branch. If source branch is being merged to dev or test branches I want one runner to run the job, but if source branch is being merged into master branch I want another gitlab-runner to run this job.

We are using Gitlab 17.2 and have a stage “test” that takes up to 4 hours to complete.
We need to use resource_group in our gitlab-ci script because if multiple “test” stages run on the same runner, the stage will crash because the database is locked during the execution of the test.

I have a GitLab instance with a Container Registry, and I want to ensure that my cleanup policy and garbage collector are configured correctly. My goal is to remove only the tags that are marked for deletion by the cleanup policy and not touch any other tags.

Gitlab runner automatically masks certain CI/CD variables (on protected branch pipelines), that looks like UUIDs (like “79c14111-6272-4222-ba15-0abbb96efbc2”) to prevent accidental exposure of sensitive data.

I have established CI (shell runner). I have a simple pipeline like this:

my gitlab cicd runner is starting and at end , it is stucking without showing me the result till the timeout, and after it it is failing with timeout error