The YAML file must have the extension .yml or .yaml. You can use * and ** wildcards in the file path. You can use certain CI/CD variables. ... The .gitlab-ci.yml file and the local file must be on the same branch.

The .gitlab-ci.yml file defines the stages, jobs, and scripts that make up your CI/CD pipeline, including variables, job dependencies, and when and how each job runs.

Create a .gitlab-ci.yml file at the root of your repository.

include: - project: SocialGouv/gitlab-ci-yml file: /base_docker_kubectl_image_stage.yml ref: v23.3.4 - project: SocialGouv/gitlab-ci-yml file: /base_create_namespace_stage.yml ref: v23.3.4 # Create namespace: extends: .base_create_namespace_stage variables: # The rancher project where the namespaces will be created RANCHER_PROJECT_ID: <rancher_project_id> # Optional REMOTE_URL: "https://github.com/${CI_PROJECT_PATH}.git" before_script: - K8S_NAMESPACE=my-namespace # (re)create to ensure a new namespaces will be created # - kubectl delete namespaces ${K8S_NAMESPACE} || true

The .gitlab-ci.yml file defines scripts that should be run during the CI/CD pipeline and their scheduling, additional configuration files and templates, dependencies, caches, commands GitLab should run sequentially or in parallel, and instructions ...

June 20, 2023 - Hello, I am new to Gitlab and trying to understand existing gitlab-ci.yml files. I have gone through below include section in the file, where i have noticed ‘.’ below the file name in file: “.poc-template-v4.yml”. What is that purpose of ‘.’ please help me know. include: - project: ...

if: '($CI_PIPELINE_SOURCE == "merge_request_event" && $CI_MERGE_REQUEST_EVENT_TYPE != "merge_train") && $CI_MERGE_REQUEST_LABELS =~ /pipeline:run-with-rails-next/' ... workflow: name: '$PIPELINE_NAME' rules: # https://gitlab.com/gitlab-org/gitlab/-/issues/514740 - if: '$GITLAB_USER_LOGIN == "gitlab-crowdin-bot" && $CI_PIPELINE_SOURCE == "merge_request_event" && $CI_MERGE_REQUEST_APPROVED != "true"' when: never - if: '$CI_PIPELINE_SOURCE == "pipeline" && $GITALY_TEST' variables: <<: *default-ruby-variables PIPELINE_NAME: 'Gitaly Rails Test Pipeline' - <<: *if-triggered-by-aigw-project variables: <<: *default-ruby-variables PIPELINE_NAME: 'AIGW Rails Test Pipeline' # If `$FORCE_GITLAB_CI` is set, create a pipeline.

1 week ago - The GitLab CI configurations are specified using a YAML file called .gitlab-ci.yml.

A file called .gitlab-ci.yml in the root of your repository, which contains the CI/CD configuration.

September 15, 2025 - The .gitlab-ci.yml file is used to define your project’s stages and jobs. It spans the entire DevOps lifecycle and configures all the CI/CD pipelines in your project, from code tests through to deployments.

October 16, 2023 - GitLab CI/CD is a powerful tool that utilizes a YAML configuration file .gitlab-ci.yml within each code repository.

To add a job to a pipeline, add it into your .gitlab-ci.yml file.

July 23, 2025 - The .gitlab-ci.yml file is a YAML-based configuration file placed in the root of your GitLab repository. It tells GitLab how to run CI/CD jobs, which include steps such as compiling code, running tests, deploying applications, and more.

CI/CD pipelines are the fundamental component of GitLab CI/CD. Pipelines are configured in a .gitlab-ci.yml file by using YAML keywords.

February 16, 2026 - At its heart, the .gitlab-ci.yml file is just a text file that speaks YAML. This format uses indentation specifically spaces, not tabs—to map out the hierarchy and relationships between different parts of your pipeline.

Cloud Native GitLab Helm Chart

Examples and community-contributed guides for implementing GitLab CI/CD across languages, frameworks, and deployment targets.

GitLab Tutorials: Example of .gitlab-ci.yml. GitHub Gist: instantly share code, notes, and snippets.