Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with how result.summary.status gets set #687

Open
freefood89 opened this issue Dec 29, 2023 · 0 comments
Open

Problem with how result.summary.status gets set #687

freefood89 opened this issue Dec 29, 2023 · 0 comments

Comments

@freefood89
Copy link
Contributor

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:

  • 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

@freefood89 freefood89 changed the title Problem with how results.summary.status gets set Problem with how result.summary.status gets set Dec 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant