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

Use the status of step as a parameter in the next step #3220

Closed
nmousouros opened this issue Sep 14, 2020 · 4 comments
Closed

Use the status of step as a parameter in the next step #3220

nmousouros opened this issue Sep 14, 2020 · 4 comments
Labels
kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@nmousouros
Copy link

Is it possible to get the status of the task ( success/ failure) as a result or as a variable or parameter?

I am trying to configure secured branches in github and I want to notify it only if the tests in the pipeline succeed or notify failure if it fails

@bobcatfish
Copy link
Collaborator

Hey @nmousouros - if a Task in a pipeline fails, the whole pipeline stops. The exception is "finally" tasks, which run after the rest of the pipeline, regardless of failure, and for those we are planning to add #1020 which would allow finally tasks to see the state of the rest fo the pipeline

@bobcatfish bobcatfish added the kind/question Issues or PRs that are questions around the project or a particular feature label Sep 15, 2020
@tekton-robot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale with a justification.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle stale

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 14, 2020
@tekton-robot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten with a justification.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close with a justification.
If this issue should be exempted, mark the issue as frozen with /lifecycle frozen with a justification.

/lifecycle rotten

Send feedback to tektoncd/plumbing.

@tekton-robot tekton-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 13, 2021
@bobcatfish
Copy link
Collaborator

I think this request is very similar to #2800 and also #1559, gonna close this issue for now, but please reopen or comment in those issues (or the WIP TEP tektoncd/community#302) if we are missing something!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/question Issues or PRs that are questions around the project or a particular feature lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants