This page is currently a draft. More information and discussion about changes to this draft may be on thediscussion page. Comprehensive documentation will come with time. You can help by adding tips and solutions to problems as you encounter them.

Here you will find some tips for getting startedusing gitlab-ci to test commits on your project hosted atgitlab.wikimedia.org.

This is a supplement to theupstream documentation and the aim of this page is to cover differences and limitations specific to Wikimedia's GitLab CI environment.

You can configure the commands to run for your CI pipeline by creating .gitlab-ci.yaml at the root of your project repository. You can also create this file by using the web interface athttps://gitlab.wikimedia.org/yourgroup/yourproject/-/ci/editor

When using the web interface to create your CI configuration, you should be aware that the built-in templates that GitLab provides as examples for.gitlab-ci.yaml are not customized for the Wikimedia CI environment and will not work without some modifications. Specifically, you might have to change the Docker images used to run your jobs. Built-in templates point to images hosted on Docker Hub which might not be accessible to some Wikimedia CI runners (for exampletrusted runners). Instead you need to use images published onhttps://docker-registry.wikimedia.org/.

• Get started with GitLab CI/CD
• Keyword reference for the.gitlab-ci.yml file
• Deployment pipeline sandbox repository with configuration examples for Blubber and GitLab CI.

• GitLab/Workflows/Deploying services to production
• wikitech:GitLab/Gitlab Runner
• wikitech:GitLab/Gitlab Runner/Security Evaluation

• GitLab technical documentation
• Continuous integration

• Drafts