-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Finish up removal of Conditions
🧹
#5027
Conversation
In tektoncd#4942, we removed `Conditions`. However, there was some logic that was left over. In this change, we clean up the remaining logic for `Conditions`. Issue: tektoncd#3377
[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 |
The following is the coverage report on the affected files.
|
case n == "dagtask3": | ||
if !isSkipped(t, n, taskrunItem.Status.Conditions) { | ||
t.Fatalf("dag task %s should have skipped due to condition failure", n) | ||
} |
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.
for reviewers' convenience, "dagtask3" was migrated to use when expressions and is in skipped tasks section of pipelinerun status now - see line 342 to line 349
/lgtm Ooops, I did miss a little bit. =) |
Changes
In #4942, we removed
Conditions
. However, there was some logic that was left over. In this change, we clean up the remaining logic forConditions
.Issue: #3377
/kind cleanup
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes