The optional configuration
section can specify an execution environment for all steps in the pipeline. While this configuration can be defined per step, it is sometimes more convenient to define it at a pipeline level if it's going to be the same for all steps in the pipeline.
The basic format of each configuration
section is:
Tag | Description |
---|---|
| Variables defined here are available for use in every step in the pipeline. These variables are read-only; they cannot be redefined in a step. If the following variables are set, they will be used:
|
| Optionally specify a specific node pool where your steps will execute. If not specified, then the node pool set as the default will be used. For more information, see Choosing Node Pools. |
| Optionally specify an Affinity Group name to specify that all steps in this Pipeline are part of one Affinity Group. This means that all steps will run on the same build node. For more information, see Running multiple steps on the same build node. |
| This section allows you to specify the default runtime environment for steps in the pipeline. The options are:
For more information, see Choosing your Runtime Image. |
| Any runs of the pipeline will not start running while another run of the same pipeline is processing if |
| Specifies when the pipeline may run relative to other pipelines connected by resources. If any of these three settings are true, new runs will not be created for resources updated by other pipelines if there is already a waiting run with the same resources and steps. So if a pipeline runs twice consecutively and the following pipeline has waitOnParentComplete set to true, the following pipeline will only run once. When the pipelines do run, they will use the latest resource versions. The optional settings are:
|
| Optionally specify if the pipeline run data should be deleted after a specific number of days. Also, provides the ability to keep a minimum number of pipeline runs data:
For more information, see Setting Retention Policy. |
| Optionally specify either 1 to use JFrog CLI v1 or 2 to use JFrog CLI v2 in the steps in the pipeline. The default is currently v1. |
| Specifies Integrations, similar to the For more information, see Pipelines Integrations. NotePipeline-level declarations for integrations are applicable for all steps. You cannot choose the steps that will not use those integrations. |
| Specifies Resources, similar to the For more information, see Using Resources. NotePipeline-level declarations for input resources are applicable for all steps. You cannot choose the steps that will not use those input resources. |
| Specifies Resources, similar to the out For more information, see Using Resources. NotePipeline-level declarations for output resources are applicable for all steps. You cannot choose the steps that will not use those output resources. |
Any step can override the pipeline's default runtime
configuration if needed to configure its own runtime selection.