You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update environment variables that are in server (#9348)
* Update environment variables that are in server
* add note about version support for OIDC on server
* fix lint errors
* v1 token is also available from 4.4
---------
Co-authored-by: Rosie Yohannan <[email protected]>
Copy file name to clipboardExpand all lines: jekyll/_cci2/variables.adoc
+8-8
Original file line number
Diff line number
Diff line change
@@ -16,9 +16,9 @@ This page is a reference for all built-in values available for use in your Circl
16
16
[#built-in-environment-variables]
17
17
== Built-in environment variables
18
18
19
-
The following built-in environment variables are available for CircleCI projects. A few environment variables are available for GitHub OAuth and Bitbucket Cloud projects that have been deprecated for GitLab, GitHub App and Bitbucket Data Center support. If you must continue to use those as environment variables in your GitLab pipelines, refer to the workaround described after the list below.
19
+
The following built-in environment variables are available for CircleCI projects. Some environment variables are available for GitHub OAuth and Bitbucket Cloud projects that have been deprecated for GitLab, GitHub App and Bitbucket Data Center support. If you must continue to use those as environment variables in your GitLab pipelines, refer to the workaround described after the list below.
20
20
21
-
Environment variables are scoped at the job level. They can be used within the context of a job but do not exist at a pipeline level, therefore they cannot be used for any logic at the pipeline or workflow level.
21
+
Environment variables are scoped at the job level and can be used within the context of a job. Environment variables do not exist at a pipeline level, therefore they cannot be used for any logic at the pipeline or workflow level.
22
22
23
23
NOTE: You cannot use a built-in environment variable to define another environment variable. Instead, you must use a `run` step to export the new environment variables using `BASH_ENV`. For more details, see xref:set-environment-variable#set-an-environment-variable-in-a-shell-command[Setting an Environment Variable in a Shell Command].
24
24
@@ -93,28 +93,28 @@ NOTE: You cannot use a built-in environment variable to define another environme
93
93
| String
94
94
| An OpenID Connect token signed by CircleCI which includes details about the current job.
95
95
| icon:check[]
96
-
| icon:times[]
96
+
| icon:check[] from v4.4
97
97
98
98
| `CIRCLE_OIDC_TOKEN_V2`
99
99
| GitHub, Bitbucket, GitLab
100
100
| String
101
101
| An OpenID Connect token signed by CircleCI which includes details about the current job.
102
102
| icon:check[]
103
-
| icon:times[]
103
+
| icon:check[] from v4.4
104
104
105
105
| `CIRCLE_ORGANIZATION_ID`
106
106
| GitHub, Bitbucket, GitLab
107
107
| String
108
108
| A unique identifier for the CircleCI organization.
109
109
| icon:check[]
110
-
| icon:times[]
110
+
| icon:check[]
111
111
112
112
| `CIRCLE_PIPELINE_ID`
113
113
| GitHub, Bitbucket, GitLab
114
114
| String
115
115
| A unique identifier for the current pipeline.
116
116
| icon:check[]
117
-
| icon:times[]
117
+
| icon:check[]
118
118
119
119
| `CIRCLE_PR_NUMBER`
120
120
| GitHub OAuth, Bitbucket Cloud
@@ -140,7 +140,7 @@ NOTE: You cannot use a built-in environment variable to define another environme
140
140
| `CIRCLE_PREVIOUS_BUILD_NUM`
141
141
| GitHub, Bitbucket, GitLab
142
142
| Integer
143
-
| The largest job number in a given branch that is less than the current job number. **Note**: The variable is not always set, and is not deterministic. It is also not set on runner executors. This variable is likely to be deprecated, and CircleCI recommends users to avoid using it.
143
+
| The largest job number in a given branch that is less than the current job number. **Note**: The variable is not always set, and is not deterministic. It is also not set on runner executors. This variable will be deprecated and is not recommended for use.
144
144
| icon:check[]
145
145
| icon:check[]
146
146
@@ -149,7 +149,7 @@ NOTE: You cannot use a built-in environment variable to define another environme
0 commit comments