Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitfb8171a

Browse files
committed
Update specifications.md
1 parentd508368 commitfb8171a

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

‎_docs/pipelines/specifications.md‎

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,8 +92,8 @@ The priority (override behavior) is as follows, from highest to lowest:
9292
|`spec.requiredAvailableStorage`| The minimum disk space for the pipeline’s build volume in`Gi`. <br> When defined, Codefresh assigns either a cached disk with sufficient disk space or a new empty disk at the start of the build. <br>When empty, only the space not allocated for caching is available for the build volume. <br>See[Set minimum disk space for a pipeline build]({{site.baseurl}}/docs/pipelines/pipelines/#set-minimum-disk-space-for-a-pipeline-build).| string| Optional|
9393
|`spec.lowMemoryWarningThreshold`| The memory-usage threshold for the pipeline's build exceeding which to display banner alerts. Useful to get timely warnings and prevent build failures. <br>Can be one of the following:{::nomarkdown}<ul><li><b>WARNING</b>: Displays a banner when memory usage exceeds 70% of the available memory. </li><li><b>CRITICAL</b>: Displays a banner when memory usage exceeds 90% of the available memory. </li><li><b>REACHED_LIMIT</b>: Displays a banner when memory usage exceeds 100% of the available memory. Setting this threshold means that the pipeline build has already failed when the banner is displayed.</li></ul>{:/}See also[Set memory usage threshold for pipeline build]({{site.baseurl}}/docs/pipelines/pipelines/#set-memory-usage-threshold-for-pipeline-build).| string| Optional|
9494
|`spec.packId`| Required for SaaS environments. Optional for hybrid environments.<br>The package identifier based on the resource size. Can be one of the following:{::nomarkdown}<ul><li><codeclass="highlighter-rouge">5cd1746617313f468d669013</code>: Small</li><li><codeclass="highlighter-rouge">5cd1746717313f468d669014</code>: Medium</li><li><codeclass="highlighter-rouge">5cd1746817313f468d669015</code>: Large</li><li><codeclass="highlighter-rouge">5cd1746817313f468d669017</code>: Extra large</li><li><codeclass="highlighter-rouge">5cd1746817313f468d669018</code>: XXL</li><li><codeclass="highlighter-rouge">5cd1746817313f468d669020</code>: 4XL</li></ul>{:/}| string| Required (for SaaS)|
95-
|`spec.contexts`| Single or multiple comma-separated shared configuration contexts, including shared secrets to add to the pipeline. <br>See[Shared configuration contexts]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/).| array| Optional|
96-
|`spec.clustersInfo`| Determines if all or specific Kubernetes clusters are available for the pipeline build. Leave empty to inherit the account-level setting.(NIMA: how can the user know what the account-level setting is? Do they have to go manually to the Settings to see if there are restrictions?) <br>See[Select Kubernetes cluster contexts]({{site.baseurl}}/docs/pipelines/pipelines/#select-kubernetes-cluster-contexts).| object| Optional|
95+
|`spec.context`| Single or multiple comma-separated shared configuration contexts, including shared secrets to add to the pipeline. <br>See[Shared configuration contexts]({{site.baseurl}}/docs/pipelines/configuration/shared-configuration/).| array| Optional|
96+
|`spec.clustersInfo`| Determines if all or specific Kubernetes clusters are available for the pipeline build. Leave empty to inherit the account-level setting.<!--- how can the user know what the account-level setting is? Do they have to go manually to the Settings to see if there are restrictions?--> <br>See[Select Kubernetes cluster contexts]({{site.baseurl}}/docs/pipelines/pipelines/#select-kubernetes-cluster-contexts).| object| Optional|
9797
|`spec.variables`| The variables defined in the pipeline. See[spec.variables](#specvariables).| array| Optional|
9898
|`spec.specTemplate`| See[spec.specTemplate](#specspectemplate).| object| Optional|
9999
|`spec.steps`| The steps to be executed by the pipeline, as a list of key-value pairs. <br>See[Steps in pipelines]({{site.baseurl}}/docs/pipelines/steps/).| object| Required|
@@ -141,6 +141,7 @@ The priority (override behavior) is as follows, from highest to lowest:
141141
|`spec.triggers.gerritCIStatusLabels`| The labels indicating the CI status.| array| Optional|
142142
|`spec.triggers.context`| The name of the Git integration to use.| string| Optional|
143143
|`spec.triggers.concurrency`| The maximum number of concurrent builds for this trigger, and can range from`1` (the default), to`15`, or unlimited). Define the trigger concurrency when your pipeline has multiple triggers.| string| Optional|
144+
|`spec.triggers.priority`| ??| integer| Optional|
144145
|`spec.triggers.terminationPolicy`| The options that determine when to terminate the build from the pipeline. See[spec.terminationPolicy](#specterminationpolicy).| integer| Optional|
145146

146147

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp