Translating the deprecated gitlab ci “only” into “rules”
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:
Translating the deprecated gitlab ci “only” into “rules”
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:
Translating the deprecated gitlab ci “only” into “rules”
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:
Translating the deprecated gitlab ci “only” into “rules”
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:
Translating the deprecated gitlab ci “only” into “rules”
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:
Group access tokens not visible in GitLab in CI job ran outside main branch
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).
Running Gitlab CI/CD job on main branch but job should not run on MR from main to other branches
I have added gitlab CI/CD job which should run after a MR is merged to master.
Running Gitlab CI/CD job onmain branch but job should not run on MR from main to other branches
I have added gitlab CI/CD job which should run after a MR is merged to master.
GitLab UI variables not available in grandchild pipeline
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.
GitLab UI variables not available in grandchild pipeline
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.