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.

I have a pipeline that has multiple jobs each producing two types of artifacts – headers inside include directory and library binaries inside lib directory. I download these artifacts during the configuration stage of a CMake project using FetchContent.

This is my gitlab pipeline setup. I have a deploy task that deploys the code and backup task that backups the database. But I keep getting this error:

I’m trying to deploy code from a Gitlab repository into remote servers.

I have a Gitlab pipeline and I want certain jobs to only run if certain files have changes from the previous commit. Here’s my code:

I have a Gitlab pipeline that builds Docker containers using something similar to this template. Instead of logging in with username/password I want to use a Docker config.json file to authenticate. I uploaded the config.json to the secure files in the project. Now I’m trying to download the secure file following these procedures but since I’m using the docker:cli image, there’s no curl or bash.

I have a Gitlab pipeline and I want to include another pipeline. I want to run it multiple times, but with different inputs each time. Something like this:

I’ve a GitLab CI and try to create a rule based on CI_MERGE_REQUEST_TITLE predefined variable. When I print all env variable with env keyword, CI_MERGE_REQUEST_TITLE doesn’t exist. But it’s written in official documentation. Why is that?

I’ve a GitLab CI and try to create a rule based on CI_MERGE_REQUEST_TITLE predefined variable. When I print all env variable with env keyword, CI_MERGE_REQUEST_TITLE doesn’t exist. But it’s written in official documentation. Why is that?

I am having an issue with a test run being stuck via a GitLab pipeline, though it does work when I run my test locally. I have found the common issue which is it gets stuck when trying to call an external URL.