PipelineUpdateInput
INPUT_OBJECT
Autogenerated input type of PipelineUpdate
Input Fields |
---|
A unique identifier for the client performing the mutation. |
|
The |
A description of this pipeline. |
An emoji to represent this pipeline. |
A color hex code to represent this pipeline. |
The visibility of the pipeline, either PUBLIC or PRIVATE. |
A source code repository that will back this pipeline |
Steps used by this pipeline defined as YAML |
The default branch used to show statistics about the build |
The next build number to use in the sequence |
If intermediate builds should be skipped as new builds are created |
A branch filter to scope which builds this is applied to |
If intermediate builds should be canceled as new builds are created |
A branch filter to scope which builds this is applied to |
If existing builds can be rebuilt as new builds. Default value: true |
The default timeout in minutes for all command steps in this pipeline. This can still be overridden in any command step. |
The maximum timeout in minutes for all command steps in this pipeline. Any command step without a timeout or with a timeout greater than this value will be set to this value. |
Choose to keep builds or remove them after a set time period. Pipelines are scanned once a day for builds that can be removed according to these settings. Some billing plans require this setting to be enabled. |
How long is a build kept before it is automatically removed. |
The minimum number of builds to keep in the pipeline regardless of how old the builds are. |
The GraphQL ID of the cluster you want to update for the pipeline |
Whether or not this pipeline should be archived. This field is deprecated and will be removed on 2022-06-01. Use ArchivePipeline and UnarchivePipeline mutations instead. |
Tags you want this pipeline to have |
A branch filter pattern to limit which pushed branches trigger builds on this pipeline. |