GitLab · Run a pipeline — Starts a CI/CD pipeline on a branch — runs the project's .gitlab-ci.yml on a branch, as Run pipeline in GitLab does. Use it to deploy, build or run a job from a Bizomate workflow.

Who can do this

Workspace Admins and Editors, on every plan. Viewers see the step's settings but cannot change them.

Before you start

  • A GitLab connection with the api scope, whose user is a Developer or above in the project — see Connect GitLab.
  • A .gitlab-ci.yml file on the branch.

Steps

  1. Select + where the step should go. In the step picker, open Apps, select GitLab, then Run a pipeline. Or search GitLab.
  2. In Connection, choose your GitLab connection.
  3. In Project, choose the project — for example consulace/billing-service.
  4. In Branch, choose the branch to run on — main.
  5. Optional: under Variables, select Add a field for each variable — Variables for this pipeline, as its .gitlab-ci.yml names them. Type its name in the first box — DEPLOY_ENV — and its value in Value — production, or a value from an earlier step.
  6. Select Run this step to try it. This starts a real pipeline.

Output

Field What it is
id GitLab's id for the pipeline.
status Where it stands when started — usually created or pending.
ref The branch it runs on.
url The pipeline's page in GitLab.

Good to know

  • The step does not wait for the pipeline to finish. To act when it does, start another workflow with GitLab · Pipeline finished — see Start a workflow from GitLab events.
  • Variables are sent as text, and take the place of a variable of the same name set in the project's CI/CD settings for this pipeline.
  • Running on a protected branch needs the token's user to be allowed to merge or push to it.
  • Each item runs the step once. Ten items start ten pipelines.

If something goes wrong

What you see Why What to do
GitLab refused: Missing CI config file. The branch has no .gitlab-ci.yml. Add one, or choose another branch.
GitLab refused: Pipeline will not run for the selected trigger. … The file's rules leave out every job for a pipeline started this way. Check the jobs' rules or only in the file.
GitLab refused: 403 Forbidden. Check the connection's details on Connections. The token's user may not run pipelines on this branch. Give the user the Developer role, or the right to the protected branch.
Branch is empty when the step ran — an earlier step may not have given the value it names. No branch. Choose it from the list.
Nothing to pick — "This project has no branches yet." The repository is empty. Push a first commit in GitLab, then Refresh.