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
Users now have the ability to explicitly start a PipelineRun using the
/test comment, irrespective of whether the pipelinerun matches the
annotations. This feature grants users explicit control over the
execution of PipelineRuns for specific types of Pull Requests, allowing
manual initiation instead of relying solely on events.
This enhancement is particularly useful for scenarios where users need
fine-grained control over the testing process, such as for Pull Requests
managed by users rather than events.
Add e2e for gitlab/github(ghe)/gitea
Jira: https://issues.redhat.com/browse/SRVKP-3561
Signed-off-by: Chmouel Boudjnah <chmouel@redhat.com>
To trigger GitOps commands in response to a push request, you can include `GitOps`
150
-
comments within your commit messages. These comments can be used to restart
151
-
either all pipelines or specific ones. Here's how it works:
148
+
If you want to trigger a GitOps command on a pushed commit, you can include the
149
+
`GitOps`comments within your commit messages. These comments can be used to
150
+
restart either all pipelines or specific ones. Here's how it works:
152
151
153
152
For restarting all pipeline runs:
154
153
@@ -185,7 +184,7 @@ located, with the context of the **test** branch.
185
184
3. `/retest <pipelinerun-name> branch:test`
186
185
4. `/test <pipelinerun-name> branch:test`
187
186
188
-
To add `GitOps` comments to a push request, follow these steps:
187
+
To issue a `GitOps` comment on a pushed commit you can follow these steps:
189
188
190
189
1. Go to your repository.
191
190
2. Click on the **Commits** section.
@@ -196,12 +195,25 @@ To add `GitOps` comments to a push request, follow these steps:
196
195
197
196
Please note that this feature is supported for the GitHub provider only.
198
197
199
-
## Cancelling the PipelineRun
198
+
### GitOps commands on non-matching PipelineRun
199
+
200
+
The PipelineRun will be restarted regardless of the annotations if the comment
201
+
`/test <pipelinerun-name>`or `/retest <pipelinerun-name>` is used . This let
202
+
you have control of PipelineRuns that gets only triggered by a comment on the
203
+
pull request.
204
+
205
+
### Custom GitOps commands
206
+
207
+
Using the [on-comment]({{< relref "/docs/guide/authoringprs.md#matching-a-pipelinerun-on-a-regexp-in-a-comment" >}}) annotation on your `PipelineRun` you can define custom GitOps commands that will be triggered by the comments on the pull request.
208
+
209
+
See the [on-comment]({{< relref "/docs/guide/authoringprs.md#matching-a-pipelinerun-on-a-regexp-in-a-comment" >}}) guide for more information.
210
+
211
+
## Cancelling a PipelineRun
200
212
201
213
You can cancel a running PipelineRun by commenting on the PullRequest.
202
214
203
215
For example if you want to cancel all your PipelinerRuns you can add a comment starting
204
-
with `/cancel` and all PipelineRun attached to that pull or merge request will be cancelled.
216
+
with `/cancel` and all PipelineRun attached to that pull request will be cancelled.
0 commit comments