cbe787c587
Explain CI_PROJECT_NAMESPACE better ## What does this MR do? Explain CI_PROJECT_NAMESPACE better by adding "The project namespace (username or groupname) that is currently being built". ## Are there points in the code the reviewer needs to double check? Are `username` and `groupname` known words? We use it [here](http://docs.gitlab.com/ee/api/namespaces.html). ## Why was this MR needed? Because `namespace` isn't a well known term. ## What are the relevant issue numbers? ## Screenshots (if relevant) See merge request !5407 |
||
|---|---|---|
| .. | ||
| api | ||
| build_artifacts | ||
| docker | ||
| examples | ||
| img | ||
| permissions | ||
| quick_start | ||
| runners | ||
| services | ||
| ssh_keys | ||
| triggers | ||
| variables | ||
| yaml | ||
| README.md | ||
| enable_or_disable_ci.md | ||
| environments.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
- API
- CI services (linked docker containers)