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
Is this working as intended? Am I using Tekton Triggers wrong?
Background
I have 2 Triggers that each create a PipelineRun:
sonar scan pipeline
unit test pipeline
Problem
The result.summary.status=SUCCESS when the sonar scan PipelineRun has status.conditions.0.reason=Succeeded and the unittest PipelineRun has status.conditions.0.reason=Failed
It looks like this happens because the result name is derived from the eventid as follows: <namespace>/results/<eventid> so when a single event matches 2 Triggers the result.summary.status takes the status condition from only one of the PipelineRuns. In my case they took the condition from the PipelineRun that started first and finished first.
Workaround
I will just use the status conditions directly from the base64 encoded record data to get results for each PipelineRun
The text was updated successfully, but these errors were encountered:
freefood89
changed the title
Problem with how results.summary.status gets set
Problem with how result.summary.status gets set
Dec 29, 2023
Version
v0.8.1 deployed via manifests
Is this working as intended? Am I using Tekton Triggers wrong?
Background
I have 2 Triggers that each create a PipelineRun:
Problem
The
result.summary.status=SUCCESS
when the sonar scan PipelineRun hasstatus.conditions.0.reason=Succeeded
and the unittest PipelineRun hasstatus.conditions.0.reason=Failed
It looks like this happens because the result name is derived from the eventid as follows:
<namespace>/results/<eventid>
so when a single event matches 2 Triggers theresult.summary.status
takes the status condition from only one of the PipelineRuns. In my case they took the condition from the PipelineRun that started first and finished first.Workaround
I will just use the status conditions directly from the base64 encoded record data to get results for each PipelineRun
The text was updated successfully, but these errors were encountered: