> For the complete documentation index, see [llms.txt](https://docs.earthbuild.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.earthbuild.dev/ci-integration/vendor-specific-guides/gitlab-integration.md).

# GitLab CI/CD

This example uses [GitLab CI/CD](https://docs.gitlab.com/ee/ci/) to build the EarthBuild target `+build`.

```yml
# .gitlab-ci.yml

services:
- docker:dind

variables:
  DOCKER_HOST: tcp://docker:2375
  FORCE_COLOR: 1
  EARTH_EXEC_CMD: "/bin/sh"

image: earthbuild/earthbuild:v0.8.19

before_script:
- docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY

earth:
  stage: build
  script:
- earth --ci --push -P +build
```

Note that in this particular configuration, the `earthbuild/earthbuild` image will first start BuildKit under the same container via the image's entrypoint script; however by setting `EARTH_EXEC_CMD=/bin/sh`, the `/usr/bin/earth-entrypoint.sh` script will present a shell rather than call the earth binary. This bootstrapping occurs before the `before_script` portion of the gitlab job executes.

In order to configure a registry mirror, users will need to configure a multi-line string for `EARTH_ADDITIONAL_BUILDKIT_CONFIG` under the `variables` section. For example:

```yml
variables:
  EARTH_ADDITIONAL_BUILDKIT_CONFIG: |-
    [registry."docker.io"]
      mirrors = ["registry-mirror.example.com"]
```

A full example is available [on GitLab](https://gitlab.com/earthly-technologies/earthly-demo).

For a complete guide on CI integration see the [CI integration guide](/ci-integration/overview.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.earthbuild.dev/ci-integration/vendor-specific-guides/gitlab-integration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.