tektoncd/pipeline

TEP 0097: Add `breakpoints`, `breakpoints.onFailure` to `debug` and extend support to PipelineRun

Open

#5,184 opened on Jul 21, 2022

View on GitHub
 (13 comments) (0 reactions) (1 assignee)Go (1,943 forks)auto 404
area/apiarea/roadmaphelp wantedkind/featurekind/teplifecycle/frozen

Repository metrics

Stars
 (9,013 stars)
PR merge metrics
 (PR metrics pending)

Description

Feature request

Add breakpoints, breakpoints.onFailure to debug spec in TaskRuns which uses existing logic from the onFailure option in the debug.breakpoint spec in the TaskRun spec. Extend this logic to support PipelineRuns as well.

This will be the start development on TEP 0097 using the debug.breakpoints spec insteam of the debug.breakpoint spec to not break existing behavior. eventually deprecate debug.breakpoint in the TaskRun Spec.

Use case

Debug PipelineRuns on Failure

Contributor guide

Research direction
Study TEP 0097 to understand the proposed breakpoints design, examine the existing debug.breakpoint implementation in TaskRun, and then extend the logic to support PipelineRun while ensuring backward compatibility.
Tech stack
go
Domain
backenddevopsci cd
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoKubernetesTekton
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40