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

Commit2b10325

Browse files
committed
Update git-triggers.md
Added use case for trigger level disk space
1 parent6f16372 commit2b10325

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

‎_docs/configure-ci-cd-pipeline/triggers/git-triggers.md‎

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,9 @@ max-width="60%"
258258
**Runtime Environment*: choose to use pipeline[settings]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipelines/#pipeline-settings) or override them
259259

260260
###Set minimum disk space for build volume by trigger
261-
Set the disk space you need for the build volume in the context of the selected trigger. Setting the disk space for the trigger overrides that set for the pipeline.
261+
Set the disk space you need for the build volume in the context of the selected trigger. Setting the disk space for the trigger overrides that set for the pipeline.
262+
263+
Reserving disk space at the trigger-level is useful for example, when you have a single pipeline for multiple repositories with a trigger for each repository. If you have a large repository that requires a large amount of space for the build, you can set the disk space_only_ for this repository. This action allows the other repositories to reserve more space for caching, optimizing resource usage and performance.
262264

263265
1. In**Workflow > Triggers**, expand**Advanced Options**.
264266
1. From the Runtime Environment list, select**Override pipeline settings**, and then select the runtime for which to override the pipeline setting.

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp