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

fix(STONEINTG-897): don't require chains for failed build PLRs #873

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

dirgim
Copy link
Collaborator

@dirgim dirgim commented Sep 12, 2024

  • It's not guaranteed that a failed build pipelineRun will be processed by Tekton chains
  • The integration service still needs to process those pipelineRuns in order to remove their finalizers

Signed-off-by: dirgim kpavic@redhat.com

Maintainers will complete the following section

* It's not guaranteed that a failed build pipelineRun
  will be processed by Tekton chains
* The integration service still needs to process
  those pipelineRuns in order to remove their finalizers

Signed-off-by: dirgim <kpavic@redhat.com>

rh-pre-commit.version: 2.2.0
rh-pre-commit.check-secrets: ENABLED
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@9aebb5b). Learn more about missing BASE report.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #873   +/-   ##
=======================================
  Coverage        ?   69.12%           
=======================================
  Files           ?       43           
  Lines           ?     4447           
  Branches        ?        0           
=======================================
  Hits            ?     3074           
  Misses          ?     1054           
  Partials        ?      319           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@hongweiliu17 hongweiliu17 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants