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.

Sign up for GitHub

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

Jump to bottom

Support for TaskRuns that fail but do not then fail the PipelineRun #1394

Closed
skaegi opened this issue Oct 9, 2019 · 5 comments
Closed

Support for TaskRuns that fail but do not then fail the PipelineRun #1394

skaegi opened this issue Oct 9, 2019 · 5 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. maybe-next-milestone For consideration when planning the next milestone triage/duplicate Indicates an issue is a duplicate of other open issue.

Comments

@skaegi
Copy link
Contributor

skaegi commented Oct 9, 2019

It's not uncommon for a development pipeline to run a set of Test Tasks where some might fail however we still might want to promote the build to a manual staging/testing environment. Existing CI/CD tools handle this with a "WARN" or similar state.
@skaegi
Copy link
Contributor Author

skaegi commented Oct 9, 2019

Also see #1376

@vdemeester vdemeester added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 9, 2019
@bobcatfish bobcatfish added the maybe-next-milestone For consideration when planning the next milestone label Oct 9, 2019
@dibyom
Copy link
Member

dibyom commented Oct 17, 2019

Related: #1023

@vdemeester vdemeester mentioned this issue Dec 4, 2019
Closed
@dibyom
Copy link
Member

dibyom commented Mar 18, 2020

@skaegi can we close this and use #1376 for tracking this feature?

@dibyom dibyom added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Mar 18, 2020
@dibyom dibyom added triage/duplicate Indicates an issue is a duplicate of other open issue. and removed priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Mar 18, 2020
@vdemeester
Copy link
Member

I think so, let's close it 🙃
/close

@tekton-robot
Copy link
Collaborator

@vdemeester: Closing this issue.

In response to this:

I think so, let's close it 🙃
/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. maybe-next-milestone For consideration when planning the next milestone triage/duplicate Indicates an issue is a duplicate of other open issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@vdemeester @bobcatfish @skaegi @dibyom @tekton-robot