-
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
feat: TEP-0097 change in taskrun breakpoints api fields #6489
feat: TEP-0097 change in taskrun breakpoints api fields #6489
Conversation
/kind feature |
/assign @lbernick |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
this pr is splited from 5691, only the breakpoint api field has been adjusted |
BeforeSteps []string `json:"beforeSteps,omitempty"` | ||
// +optional | ||
// +listType=atomic | ||
Breakpoint []string `json:"breakpoint,omitempty"` | ||
AfterSteps []string `json:"afterSteps,omitempty"` |
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.
Let's scope this PR to just the change in onFailure
, i.e. let's avoid introducing beforeSteps
and afterSteps
in this PR
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.
thanks @lbernick , i have removed beforeSteps
and afterSteps
in this PR, and changed commit message and pr description
// if enabled, pause TaskRun on failure of a step | ||
// failed step will not exit | ||
// +optional | ||
OnFailure bool `json:"onFailure,omitempty"` |
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.
There was some discussion of this on the previous PR, but it looks like this is a string (not a bool) in the TEP. Let's make sure the API changes in this PR match the API changes described in the TEP.
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.
The PR for the relevant type change is here,PTAL!
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.
hi @lbernick , Onfailure
uses the string type as described in TEP
7ac0b39
to
9790600
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
9790600
to
32fb2b6
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
@@ -212,16 +212,14 @@ func combineParamSpec(p ParamSpec, paramSpecForValidation map[string]ParamSpec) | |||
return paramSpecForValidation, nil | |||
} | |||
|
|||
// validateDebug | |||
// validateDebug validates the debug section of the TaskRun. | |||
// onFailure breakpoint is only allowed to be set as enabled. |
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.
// onFailure breakpoint is only allowed to be set as enabled. | |
// if set, onFailure breakpoint must be "enabled" |
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.
good suggestion! both v1 and v1beta1 have been modified according to this suggestion
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lbernick 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 |
Thanks @chengjoey, looks good! Suggested release note: "action required: syntax change for taskRun breakpoints (alpha feature). TaskRun breakpoints are now enabled by setting "taskRun.spec.debug.breakpoints.onFailure" to "enabled"." |
32fb2b6
to
4070b89
Compare
thanks @lbernick , i have modified release-note by your suggestion |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
hi @afrittoli , you reviewed the previeous PR, could you please review this PR again?🙏 |
Issues go stale after 90d of inactivity. /lifecycle stale Send feedback to tektoncd/plumbing. |
@chengjoey please rebase this PR and I'll review it 🙏🏾 /assign |
make TaskBreakpoints struct for taskrun debug. breakpoint on failure of a step was moved to `breakpoints.onFailure` spec and onFailure breakpoint are now enabled by setting `taskRun.spec.debug.breakpoints.onFailure` to `enabled`. Signed-off-by: chengjoey <[email protected]>
4070b89
to
b054778
Compare
thanks @jerop , I've rebased this pr |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Thanks @chengjoey! Can you link other PRs in the description? It will help me understand what's been implemented and whats coming next. Here it seems like all the plumbing is good and feeding input to the Otherwise lgtm. |
Thanks @chitrangpatel, this PR is split from 5691 and make changes to the onFaileure field as Tep-0097 described, entrypointer logic is upcoming~ |
Sounds good! Thanks! |
/lgtm |
Changes
make TaskBreakpoints struct for taskrun debug.
breakpoint on failure of a step was moved to
breakpoints.onFailure
spec and onFailure breakpoint are now enabled by setting "taskRun.spec.debug.breakpoints.onFailure" to "enabled".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