Commit 2972a991 authored by Grzegorz Bizon's avatar Grzegorz Bizon 🔴

Add minor fixes in docs for job-specific variables

parent 2b1c08be
......@@ -4,8 +4,9 @@ When receiving a build from GitLab CI, the runner prepares the build environment
It starts by setting a list of **predefined variables** (Environment Variables) and a list of **user-defined variables**
The variables can be overwritten. They take precedence over each other in this order:
1. Trigger variables
1. Secure variables
1. YAML-defined job-leve variables
1. YAML-defined job-level variables
1. YAML-defined global variables
1. Predefined variables
......
......@@ -421,19 +421,14 @@ except master.
### job variables
It is possible to define build variables using a `variables` keyword on a job
level. It works basically the same way like it's global-level equivalent but
allows you to define a job specific build variables.
level. It works basically the same way as its global-level equivalent but
allows you to define job-specific build variables.
When `variables` keyword is used on a job level, it can override global YAML
When the `variables` keyword is used on a job level, it overrides global YAML
build variables and predefined variables.
Build variables priority is defined as follows:
* predefined variables
* global YAML variables
* job YAML variables
* secure variables
* trigger variables
Build variables priority is defined in
[variables documentation](../variables/README.md).
### tags
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment