BigW Consortium Gitlab

README.md 8.55 KB
Newer Older
1
## Variables
2

3 4 5 6
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:
7
1. Trigger variables
8
1. Secure variables
9
1. YAML-defined job-level variables
10
1. YAML-defined global variables
11 12 13
1. Predefined variables

For example, if you define:
14 15
1. `API_TOKEN=SECURE` as Secure Variable
1. `API_TOKEN=YAML` as YAML-defined variable
16

17
The `API_TOKEN` will take the Secure Variable value: `SECURE`.
18 19 20

### Predefined variables (Environment Variables)

21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
| Variable                | GitLab | Runner | Description |
|-------------------------|--------|--------|-------------|
| **CI**                  | all    | 0.4    | Mark that build is executed in CI environment |
| **GITLAB_CI**           | all    | all    | Mark that build is executed in GitLab CI environment |
| **CI_SERVER**           | all    | all    | Mark that build is executed in CI environment |
| **CI_SERVER_NAME**      | all    | all    | The name of CI server that is used to coordinate builds |
| **CI_SERVER_VERSION**   | all    | all    | GitLab version that is used to schedule builds |
| **CI_SERVER_REVISION**  | all    | all    | GitLab revision that is used to schedule builds |
| **CI_BUILD_ID**         | all    | all    | The unique id of the current build that GitLab CI uses internally |
| **CI_BUILD_REF**        | all    | all    | The commit revision for which project is built |
| **CI_BUILD_TAG**        | all    | 0.5    | The commit tag name. Present only when building tags. |
| **CI_BUILD_NAME**       | all    | 0.5    | The name of the build as defined in `.gitlab-ci.yml` |
| **CI_BUILD_STAGE**      | all    | 0.5    | The name of the stage as defined in `.gitlab-ci.yml` |
| **CI_BUILD_REF_NAME**   | all    | all    | The branch or tag name for which project is built |
| **CI_BUILD_REPO**       | all    | all    | The URL to clone the Git repository |
| **CI_BUILD_TRIGGERED**  | all    | 0.5    | The flag to indicate that build was [triggered] |
37
| **CI_BUILD_MANUAL**     | 8.12   | all    | The flag to indicate that build was manually started |
38
| **CI_BUILD_TOKEN**      | all    | 1.2    | Token used for authenticating with the GitLab Container Registry |
39
| **CI_PIPELINE_ID**      | 8.10   | 0.5    | The unique id of the current pipeline that GitLab CI uses internally |
40
| **CI_PROJECT_ID**       | all    | all    | The unique id of the current project that GitLab CI uses internally |
41
| **CI_PROJECT_NAME**     | 8.10   | 0.5    | The project name that is currently being built |
42
| **CI_PROJECT_NAMESPACE**| 8.10   | 0.5    | The project namespace (username or groupname) that is currently being built |
43 44
| **CI_PROJECT_PATH**     | 8.10   | 0.5    | The namespace with project name |
| **CI_PROJECT_URL**      | 8.10   | 0.5    | The HTTP address to access project |
45 46
| **CI_PROJECT_DIR**      | all    | all    | The full path where the repository is cloned and where the build is run |
| **CI_REGISTRY**         | 8.10   | 0.5    | If the Container Registry is enabled it returns the address of GitLab's Container Registry |
47
| **CI_REGISTRY_IMAGE**   | 8.10   | 0.5    | If the Container Registry is enabled for the project it returns the address of the registry tied to the specific project |
Kamil Trzcinski committed
48
| **CI_RUNNER_ID**        | 8.10   | 0.5    | The unique id of runner being used |
49
| **CI_RUNNER_DESCRIPTION** | 8.10 | 0.5    | The description of the runner as saved in GitLab |
50
| **CI_RUNNER_TAGS**      | 8.10   | 0.5    | The defined runner tags |
51
| **CI_DEBUG_TRACE**      | all    | 1.7    | Whether [debug tracing](#debug-tracing) is enabled |
52 53
| **GITLAB_USER_ID**      | 8.12   | all    | The id of the user who started the build |
| **GITLAB_USER_EMAIL**   | 8.12   | all    | The email of the user who started the build |
54 55

**Some of the variables are only available when using runner with at least defined version.**
56 57 58 59 60 61 62

Example values:

```bash
export CI_BUILD_ID="50"
export CI_BUILD_REF="1ecfd275763eff1d6b4844ea3168962458c9f27a"
export CI_BUILD_REF_NAME="master"
63
export CI_BUILD_REPO="https://gitab-ci-token:abcde-1234ABCD5678ef@gitlab.com/gitlab-org/gitlab-ce.git"
64 65 66
export CI_BUILD_TAG="1.0.0"
export CI_BUILD_NAME="spec:other"
export CI_BUILD_STAGE="test"
67
export CI_BUILD_MANUAL="true"
68
export CI_BUILD_TRIGGERED="true"
69
export CI_BUILD_TOKEN="abcde-1234ABCD5678ef"
70
export CI_PIPELINE_ID="1000"
71
export CI_PROJECT_ID="34"
72 73 74 75
export CI_PROJECT_DIR="/builds/gitlab-org/gitlab-ce"
export CI_PROJECT_NAME="gitlab-ce"
export CI_PROJECT_NAMESPACE="gitlab-org"
export CI_PROJECT_PATH="gitlab-org/gitlab-ce"
76
export CI_PROJECT_URL="https://gitlab.com/gitlab-org/gitlab-ce"
77 78
export CI_REGISTRY="registry.gitlab.com"
export CI_REGISTRY_IMAGE="registry.gitlab.com/gitlab-org/gitlab-ce"
Kamil Trzcinski committed
79 80 81
export CI_RUNNER_ID="10"
export CI_RUNNER_DESCRIPTION="my runner"
export CI_RUNNER_TAGS="docker, linux"
82
export CI_SERVER="yes"
83
export CI_SERVER_NAME="GitLab"
84 85
export CI_SERVER_REVISION="70606bf"
export CI_SERVER_VERSION="8.9.0"
86 87
export GITLAB_USER_ID="42"
export GITLAB_USER_EMAIL="alexzander@sporer.com"
88 89 90
```

### YAML-defined variables
91
**This feature requires GitLab Runner 0.5.0 or higher and GitLab CI 7.14 or higher **
92 93 94 95 96 97 98 99 100 101 102 103 104

GitLab CI allows you to add to `.gitlab-ci.yml` variables that are set in build environment.
The variables are stored in repository and are meant to store non-sensitive project configuration, ie. RAILS_ENV or DATABASE_URL.

```yaml
variables:
  DATABASE_URL: "postgres://postgres@postgres/my_database"
```

These variables can be later used in all executed commands and scripts.

The YAML-defined variables are also set to all created service containers, thus allowing to fine tune them.

105
Variables can be defined at a global level, but also at a job level.
106

107 108
More information about Docker integration can be found in [Using Docker Images](../docker/using_docker_images.md).

109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141
#### Debug tracing

> **WARNING:** Enabling debug tracing can have severe security implications. The
  output **will** contain the content of all your secure variables and any other
  secrets! The output **will** be uploaded to the GitLab server and made visible
  in build traces!

By default, GitLab Runner hides most of the details of what it is doing when
processing a job. This behaviour keeps build traces short, and prevents secrets
from being leaked into the trace unless your script writes them to the screen.

If a job isn't working as expected, this can make the problem difficult to
investigate; in these cases, you can enable debug tracing in `.gitlab-ci.yml`.
Available on GitLab Runner v1.7+, this feature enables the shell's execution
trace, resulting in a verbose build trace listing all commands that were run,
variables that were set, etc.

Before enabling this, you should ensure builds are visible to
[team members only](../../../user/permissions.md#project-features). You should
also [erase](../pipelines.md#seeing-build-traces) all generated build traces
before making them visible again.

To enable debug traces, set the `CI_DEBUG_TRACE` variable to `true`:

```yaml
job1:
  variables:
    CI_DEBUG_TRACE: "true"
```

The [example project](https://gitlab.com/gitlab-examples/ci-debug-trace)
demonstrates a working configuration, including build trace examples.

142 143 144
### User-defined variables (Secure Variables)
**This feature requires GitLab Runner 0.4.0 or higher**

145 146
GitLab CI allows you to define per-project **Secure Variables** that are set in
the build environment.
147
The secure variables are stored out of the repository (the `.gitlab-ci.yml`).
148 149 150 151
The variables are securely passed to GitLab Runner and are available in the
build environment.
It's desired method to use them for storing passwords, secret keys or whatever
you want.
152

153 154 155
**The value of the variable can be shown in build log if explicitly asked to do so.**
If your project is public or internal you can make the builds private.

156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176
Secure Variables can added by going to `Project > Variables > Add Variable`.

They will be available for all subsequent builds.

### Use variables
The variables are set as environment variables in build environment and are accessible with normal methods that are used to access such variables.
In most cases the **bash** is used to execute build script.
To access variables (predefined and user-defined) in bash environment, prefix the variable name with `$`:
```
job_name:
  script:
    - echo $CI_BUILD_ID
```

You can also list all environment variables with `export` command,
but be aware that this will also expose value of all **Secure Variables** in build log:
```
job_name:
  script:
    - export
```
177 178

[triggered]: ../triggers/README.md