> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/getting-started/ci-setup/gitlab/custom-docker-runners.md). # Custom Docker runners Gitlab CI/CD gives you the option to use your custom docker containers to execute your tests instead of directly using their built-in runners. This usually leads to the loss of git information and environment variables not be directly available, so in this case for Currents to be able to gather all the information needed you need to setup the needed environment variables accordingly. ``` GITLAB_CI=true CI_PIPELINE_ID=$CI_PIPELINE_ID CI_PIPELINE_URL=$CI_PIPELINE_URL CI_BUILD_ID=$CI_BUILD_ID CI_JOB_ID=$CI_JOB_ID CI_JOB_URL=$CI_JOB_URL CI_JOB_NAME=$CI_JOB_NAME GITLAB_HOST=$GITLAB_HOST CI_PROJECT_ID=$CI_PROJECT_ID CI_PROJECT_URL=$CI_PROJECT_URL CI_REPOSITORY_URL=$CI_REPOSITORY_URL CI_ENVIRONMENT_URL=$CI_ENVIRONMENT_URL CI_DEFAULT_BRANCH=$CI_DEFAULT_BRANCH COMMIT_INFO_BRANCH=$CI_COMMIT_BRANCH COMMIT_INFO_MESSAGE=$CI_COMMIT_MESSAGE COMMIT_INFO_SHA=$CI_COMMIT_SHA COMMIT_INFO_REMOTE=$CI_REPOSITORY_URL ``` Adding these environment variables to your `.yml` file will allow your custom docker runner to report the correct information to Currents and have all the available information in the dashboard to use it as a usual Gitlab CI/CD tests execution. ## Fallback: Using CURRENTS\_CI\_URL If your GitLab environment variables are not forwarded to the Docker container and auto-detection fails, you can explicitly provide the CI URL using the `CURRENTS_CI_URL` environment variable: ``` CURRENTS_CI_URL=$CI_JOB_URL ``` Or for GitLab pipelines: ``` CURRENTS_CI_URL=$CI_PIPELINE_URL ``` This ensures the run link in the Currents Dashboard points back to the correct GitLab job or pipeline. See [Configuration](/resources/reporters/currents-playwright/configuration.md) for more details on `CURRENTS_CI_URL`. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.currents.dev/getting-started/ci-setup/gitlab/custom-docker-runners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.