Note:- The terms and images used in this documentation relate to Github.
If the webhook is triggered due to a pull request being created or updated with code, a monitor task will be run to track and report on the status of the configured PipelineRun
that is started by the EventListener
.
-
Each webhook created in the webhooks extension console relates to three triggers registered with the webhooks extension's
EventListener
. -
The three triggers are conceptually as follows:
- run the relevant
Pipeline
for push events on this repo - run the relevant
Pipeline
for pull_request events on this repo - run a monitor
Task
for pull_request events on this repo
- run the relevant
-
A
PipelineRun
andTaskRun
are therefore created by theEventListener
merging togetherTriggerTemplates
withTriggerBindings
. -
The monitor-result-task updates the pull request, putting its status into pending.
- The monitor-result-task periodically checks the
PipelineRun
for completion and changes the pull request's status accordingly to one of success, failure or error.
- A comment is added to the pull request showing the result of the
PipelineRun
. The reported status operates as a hyperlink to the specificPipelineRun
in the Tekton Dashboard, allowing you to quickly navigate to any relevant log files. Note thatUnknown
as a status denotes that thePipelineRun
had not completed before the monitorTaskRun
reached its maximum polling duration (30 mins).