![]() [ci skip] |
||
---|---|---|
.. | ||
api | ||
build_artifacts | ||
deployment | ||
docker | ||
examples | ||
img | ||
permissions | ||
quick_start | ||
runners | ||
services | ||
ssh_keys | ||
triggers | ||
variables | ||
yaml | ||
README.md | ||
enable_or_disable_ci.md |
README.md
GitLab CI Documentation
CI User documentation
- Get started with GitLab CI
- Learn how to enable or disable GitLab CI
- Learn how
.gitlab-ci.yml
works - Configure a Runner, the application that runs your builds
- Use Docker images with GitLab Runner
- Use CI to build Docker images
- Use variables in your
.gitlab-ci.yml
- Use SSH keys in your build environment
- Trigger builds through the API
- Build artifacts
- User permissions
- API
CI Examples
- The .gitlab-ci.yml file for GitLab itself
- Test your PHP applications
- Test and deploy Ruby applications to Heroku
- Test and deploy Python applications to Heroku
- Test Clojure applications
- Using
dpl
as deployment tool - Help your favorite programming language and GitLab by sending a merge request with a guide for that language.
CI Services
GitLab CI uses the services
keyword to define what docker containers should
be linked with your base image. Below is a list of examples you may use: