I’m trying to have access to these predefined variables for merge requests pipelines in GitLab, but apparently my pipeline is set up as basic pipelines, thus having access only to these variables. I basically need only the CI_MERGE_REQUEST_ID var. What do I need to configure (in terms of .gitlab-ci.yml, project, etc) in order to “convert” a basic pipeline into a merge request pipeline in GitLab?

I have a lot of pipelines where I build things, and then the deployment runs on releases and is triggerd by a pipeline trigger. So to only run build/test jobs when pushing to gitlab, I have this:

I have a lot of pipelines where I build things, and then the deployment runs on releases and is triggerd by a pipeline trigger. So to only run build/test jobs when pushing to gitlab, I have this:

I have a lot of pipelines where I build things, and then the deployment runs on releases and is triggerd by a pipeline trigger. So to only run build/test jobs when pushing to gitlab, I have this:

I have a lot of pipelines where I build things, and then the deployment runs on releases and is triggerd by a pipeline trigger. So to only run build/test jobs when pushing to gitlab, I have this:

I have a lot of pipelines where I build things, and then the deployment runs on releases and is triggerd by a pipeline trigger. So to only run build/test jobs when pushing to gitlab, I have this:

I am using a group access token (GAT) to download artifacts from one private repository into another and use those during the build step. Both repos are on the same self-hosted community edition instance (I am just a user, not an admin).

I have added gitlab CI/CD job which should run after a MR is merged to master.

I have added gitlab CI/CD job which should run after a MR is merged to master.

I have a CI pipeline in GitLab that triggers a child pipeline that then triggers another child pipeline. Variables that are set in the UI are available in the first child pipeline but not the second (grand)child pipeline. I have looked through the GitLab documentation on all this, I think this is configured correctly. I don’t see anything that should prevent these variables from being seen. All of this is in a single repository.