You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/docs/install/settings.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -139,6 +139,32 @@ There is a few things you can configure through the config map
139
139
risk and should be aware of the potential security vulnerabilities.
140
140
(only GitHub and Gitea is supported at the moment).
141
141
142
+
### Global Cancel In Progress Settings
143
+
144
+
* `enable-cancel-in-progress-on-pull-requests`
145
+
146
+
If the `enable-cancel-in-progress-on-pull-requests` setting is enabled (true), Pipelines-as-Code will automatically cancel
147
+
any in-progress PipelineRuns associated with a pull request when a new update (such as a new commit) is pushed to that pull request.
148
+
This ensures that only the latest commit is processed, helping conserve compute resources and avoid running outdated PipelineRuns
149
+
tied to previous commits.
150
+
151
+
It's important to note that if this global setting is disabled (false), Pipelines-as-Code will still honor the cancel-in-progress annotation
152
+
at the individual PipelineRun level. In such cases, if a PipelineRun includes this annotation, it will take precedence over the global setting,
153
+
and Pipelines-as-Code will cancel any matching in-progress runs when the pull request is updated.
154
+
155
+
This is disabled by default.
156
+
157
+
* `enable-cancel-in-progress-on-push`
158
+
159
+
If the `enable-cancel-in-progress-on-push` setting is enabled (true), Pipelines-as-Code will automatically cancel any in-progress PipelineRuns
160
+
triggered by a push event when a new push is made to the same branch. This helps ensure that only the most recent commit is processed, preventing unnecessary execution of outdated PipelineRuns and optimizing resource usage.
161
+
162
+
Additionally, if this global setting is disabled (false), Pipelines-as-Code will still respect the cancel-in-progress annotation
163
+
on individual PipelineRuns. In such cases, the annotation will override the global configuration, and Pipelines-as-Code will
164
+
cancel any in-progress runs for that specific PipelineRun when a new push occurs on the same branch.
165
+
166
+
This is disabled by default.
167
+
142
168
### Tekton Hub support
143
169
144
170
Pipelines-as-Code supports fetching task with its remote annotations feature, by default it will fetch it from the [public tekton hub](https://hub.tekton.dev/) but you can configure it to point to your own with these settings:
"Warning: The Pipelinerun '%s' has 'on-cel-expression' defined along with [%s] annotation(s). The 'on-cel-expression' will take precedence and these annotations will be ignored",
`Warning: The Pipelinerun 'pipeline-on-cel-test' has 'on-cel-expression' defined along with [on-event, on-target-branch] annotation(s). The 'on-cel-expression' will take precedence and these annotations will be ignored`,
0 commit comments