c345edcb7f
GitLab 8.12 introduced a new permissions model which tightened the security of Container Registry. It is now required to use a personal token if 2FA is enabled. [ci skip] |
||
|---|---|---|
| .. | ||
| api | ||
| build_artifacts | ||
| docker | ||
| examples | ||
| img | ||
| permissions | ||
| quick_start | ||
| review_apps | ||
| runners | ||
| services | ||
| ssh_keys | ||
| triggers | ||
| variables | ||
| yaml | ||
| README.md | ||
| enable_or_disable_ci.md | ||
| environments.md | ||
| git_submodules.md | ||
| pipelines.md | ||
README.md
GitLab CI Documentation
CI User documentation
- Get started with GitLab CI
- CI examples for various languages
- Learn how to enable or disable GitLab CI
- Pipelines and builds
- Environments and deployments
- Learn how
.gitlab-ci.ymlworks - 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
- Build permissions
- API
- CI services (linked docker containers)
- CI/CD pipelines settings
- Review Apps
- Git submodules Using Git submodules in your CI jobs
Breaking changes
- New CI build permissions model Read about what changed in GitLab 8.12 and how that affects your builds. There's a new way to access your Git submodules and LFS objects in builds.