管道Environment Variables

Standard Environment Variables

These environment variables are available to all executing pipelines.

管道

A pipeline can declare environment variables in itsconfiguration.The environment variables declared here are are available to all steps in the pipeline.

pipelines: - name: my_pipeline configuration: environmentVariables: readOnly: env1: value1 env2: value2

Steps

A step can declare environment variables in itsconfigurationof a step within a pipeline.

steps: - name: step_1 type: Bash configuration: environmentVariables: env1: value1 env2: value2

The environment variables from this source are available only to the step where they are declared.

Integrations

A step that uses an integration can access an integration's properties through environment variables. The form of the environment variable is:

int__

For example, you can access the URL property of anArtifactory IntegrationnamedmyArtifactorythrough an environment variable:

$ printenv int_myArtifactory_url https://mycompany.com/artifactory/

You can also access the properties of an integration through a resource that uses it. The form of the environment variable is:

res___

For example, anImageresource specifies an Artifactory integration in itsregistrytag. So you can access the URL of the Artifactory integration used by an Image resource calledmyImageas follows:

$ printenv res_myImage_registry_url https://mycompany.com/artifactory/

For further information see管道Integrations.

2022世界杯阿根廷预选赛赛程

A step that specifies a resource ininputresourcescan access the properties of that resource through environment variables. The form of the environment variable is:

res__

For example, you can access theimageNameproperty of anImageresourcemyImagethrough an environment variable:

$ printenv res_myImage_imageName jfrog.local:5000/alpine37

一些资源维2022世界杯阿根廷预选赛赛程护additional properties that may be accessed as environment variables. These resource types include:

• GitRepo

For further information see管道Resources.

Resource-Based State

Additionally, you can add your own properties to a resource that is specified inoutputresourcesusing thewrite_outpututility function. This can be used to createstateful pipelines.

The newly attached properties can be accessed as environment variables of the formres_{Resource Name}_{Key Name}.For example:

write_output myImage sport="baseball" equipment="bat" field="diamond"

will create three properties in the resourcemyImage. When the resource is specified in a step'sinputsources, these properties can be accessed as the following environment variables:

$ printenv res_myImage_baseball baseball $ printenv res_myImage_equipment bat $ printenv res_myImage_field diamond

For more information on run state, seeCreating Stateful Pipelines.

Run State

Your pipeline can define its own environment variables and add them to the pipeline's run state. These will be available to all steps in the run of the pipeline.

Use theutility functions for run state managementto add new environment variables to the current run state. For example, the following line in the execution block of a step:

add_run_variables hero="Superman" villain="Lex Luthor"

will create two environment variables available to the current and all future steps of the pipeline's run:

$ printenv hero Superman $ printenv villain Lex Luthor

For more information on run state, seeCreating Stateful Pipelines.

Pipeline State

Your pipeline can define its own environment variables and add them to the pipeline state. These will be available to all runs of that pipeline.

Use theutility functions for pipeline state managementto add new environment variables to the current run state. For example, the following line in the execution block of a step:

add_pipeline_variables animal="dog" vegetable="carrot"

will create two environment variables available to all run of the pipeline where they were defined:

$ printenv animal dog $ printenv vegetable carrot

For more information on pipeline state, seeCreating Stateful Pipelines.