Pipelines provides the following environment variables for your use in your YAML file. For example build definition files, see Example Pipelines build definition files.
The following variables are set by the system:
Variable name | Description |
|---|---|
| The target directory into which the build artifact will be generated.
Also known as |
| Used to set timeouts (in seconds) for the |
| With a value of |
| The application ID for this job’s pipeline. |
| The realm in which the application is running. |
| The Cloud Platform application name or sitename that corresponds to the application ID. |
| The branch or tag that holds the output of the job. This variable is
also known as When using a GitHub branch during a job launched from a PR, the
SOURCE_VCS_PATH="master"
DEPLOY_VCS_PATH="pipelines-build-pr-<pr_number>"
|
| The deployment workspace. |
| With a value of |
| A reference to the last commit in the Git repository. |
| The job ID for this job. Also known as |
| The port mapped to port 22. |
| The port mapped to port 8007. |
| Specifies which SSH key will be used in a script. For more information, see Linking to specific SSH keys with a variable and Encrypting keys and variables. |
| With a value of |
| The path of the branch specified in the |
| The name of the current running event. See Events. |
| A flag to enable or disable decryption of variables. |
| The name of the file to save script execution data to. Deployment
information is stored as shown in the following example if the
{"environment":{
"PIPELINES_DEPLOYMENT_NAME":"ode184",
"PIPELINES_DEPLOYMENT_LINK":
"http:\/\/odetopipelinesode184.prod.acquia-sites.com"
}}
Note The |
| The source directory containing the build instructions. |
| Used to set timeouts (in seconds) for the |
For information about the variables key in your YAML file, see
variables:. For details about including secure (encrypted) variables in
the variables key, see Encrypting keys and variables.