-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Nr. 2 - [TEP-0056]: Update state methods to check for child PipelineRuns
.
#8878
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
base: main
Are you sure you want to change the base?
Conversation
The following is the coverage report on the affected files.
|
d4eaab4
to
68d6528
Compare
/kind feature |
[TEP-0056]: Second PR of Pipelines-in-Pipelines feature implementation. Extend existing methods in `pipelinerunstate.go` to check for child `PipelirRuns` and add new test cases. Issues tektoncd#8760, tektoncd#7166. Signed-off-by: Stanislav Jakuschevskij <[email protected]>
68d6528
to
a3ba4de
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/meow
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
1 similar comment
/retest |
/meow |
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
// if any of the dag pipeline tasks failed, change the aggregate status to failed and return | ||
if !t.IsCustomTask() && t.haveAnyTaskRunsFailed() || | ||
t.IsCustomTask() && t.haveAnyCustomRunsFailed() || | ||
t.IsChildPipeline() && t.haveAnyChildPipelineRunsFailed() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is not binary anymore, I'm not sure that !t.IsCustomTask()
is the best check anymore.
Should we use something like:
if t.IsTask() && t.haveAnyTaskRunsFailed() ||
t.IsCustomTask() && t.haveAnyCustomRunsFailed() ||
t.IsChildPipeline() && t.haveAnyChildPipelineRunsFailed() {
I guess IsTask
may not exist...
Important
Pull request number 2.
The numbering
Nr. 2 - [TEP-0056]
means the PRs must be merged in order. They build on each other.Changes
[TEP-0056]: Second PR of Pipelines-in-Pipelines feature implementation.
Extend existing methods in
pipelinerunstate.go
to check for childPipelirRuns
and add new test cases.Issue #8760, #7166.
Release notes will be added with the last PR which will make this feature functional for users.
/kind feature
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes