Add option continueAndFail on step.onError

[FaniD]

Feature request

Currently onError for steps can be set to continue or stopAndFail. In some cases, it could be beneficial to allow the taskRun to continue with the rest of the steps, but eventually fail with the exitCode of a specific step. Therefore, I'm introducing the value continueAndFail.

This is already discussed in the comments of issue #4485

Use case

I have a task that runs a test (step 1) and publishes a test report (step 2). I want to publish a test report even if step 1 fails and let the taskRun fail accordingly (step 1 exitCode).
In that case, none of the current values of onError are enough, as continue would make the taskRun succeed and stopAndFail would prevent step 2 from running.

Release Notes

A new value has been added for step.onError:
- `continueAndFail`: declares a failure with a step error after having executed all following steps

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: FaniD / name: Fani Dimou (6de8538)

[tekton-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign jeromeju after the PR has been reviewed.
You can assign the PR to them by writing /assign @jeromeju in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[FaniD]

/test check-pr-has-kind-label

[tekton-robot]

@FaniD: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test check-pr-has-kind-label

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.

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[tekton-robot]

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage-df to re-run this coverage report

File	Old Coverage	New Coverage	Delta
pkg/entrypoint/entrypointer.go	88.0%	88.2%	0.1

[FaniD]

/kind feature

[vdemeester]

SGTM, @FaniD can we also have an e2e tests validating that the Task is indeed failed.

[FaniD]

SGTM, @FaniD can we also have an e2e tests validating that the Task is indeed failed.

sure thing. I will work on this soonish