feat: update get-failed-info step SD-1405 #178
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sowecthal
force-pushed
the
feature/update-get-failed-info-step
branch
from
fba0b47 to
480ccde
Compare
sowecthal
requested review from
DanilaKazakevich,
KrawczowaKris,
MikhailKorol-saritasa,
SergeyDeminSaritasa,
darliiin,
dmitry-mightydevops,
ilya-sonich,
kseniyashaydurova,
luciano-buono,
rtest12 and
udaltsovra
as code owners
dmitry-mightydevops
requested changes
Oct 20, 2025
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
kseniyashaydurova
requested changes
Oct 21, 2025
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
charts/tekton-pipelines/templates/common/tasks/slack-notification.yaml
Outdated
Show resolved
Hide resolved
kseniyashaydurova
approved these changes
Oct 23, 2025
udaltsovra
approved these changes
Oct 24, 2025
rtest12
approved these changes
Oct 27, 2025
SergeyDeminSaritasa
approved these changes
Oct 28, 2025
ilya-sonich
approved these changes
Oct 29, 2025
DanilaKazakevich
approved these changes
Oct 29, 2025
dmitry-mightydevops
approved these changes
Oct 30, 2025
luciano-buono
approved these changes
Nov 4, 2025
KrawczowaKris
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Task: SD-1405
get-failed-infostep-build-pipelineroleUpdated how info about failed taskRuns/steps is obtained
Before, info about the reason why taskRun's step was terminated (Error/Skipped) was obtained directly from the pipelineRun's
statusfield, but since then the schema changed (https://tekton.dev/docs/pipelines/pipelineruns/#the-status-field). Currently pipelineRun has achildReferencesfield that's a list of references to each taskRun:The updated
get-failed-infostep gets the names of these taskRuns, iterates through their outputs, filters them to get the names of the failed pod, task and step from the taskRun that has theFailedstatus condition with the step that has anErrortermination reason (and not Skipped):Tested on pga-staging