[JENKINS-34185] Pipeline debugger

It's a follow-up to FOSDEM.

We need a "Pipeline Debugger", which would allow to easily attach to Pipeline, setup breakpoints and to check Pipeline context in them. Other common debugger features would be useful as well.

Both in-Jenkins and external-IDE implementations would be useful.

Related Jenkins 2.0 contributor summit notes: https://docs.google.com/document/d/1yK2J_sv1ceLYYbeLzEW8VZ3HEr8AxZcZr8GhMk6gLUY/edit#heading=h.wif2w2yslznh

---
Originally reported by oleg_nenashev, imported from: Pipeline debugger

• assignee: jglick
  
• status: Open
  
• priority: Minor
  
• component(s): workflow-cps-plugin
  
• resolution: Unresolved
  
• votes: 13
  
• watchers: 16
  
• imported: 2025-12-07
  

It's a follow-up to FOSDEM.


We need a "Pipeline Debugger", which would allow to easily attach to Pipeline, setup breakpoints and to check Pipeline context in them. Other common debugger features would be useful as well.


Both in-Jenkins and external-IDE implementations would be useful.


Related Jenkins 2.0 contributor summit notes: https://docs.google.com/document/d/1yK2J_sv1ceLYYbeLzEW8VZ3HEr8AxZcZr8GhMk6gLUY/edit#heading=h.wif2w2yslznh 

Start by reviewing the workflow-cps-plugin context and the linked Jenkins 2.0 contributor summit notes; the issue does not name a source file, test, or entry point. Define a concrete first debugger scope covering attachment, breakpoints, and Pipeline context inspection, then use those capabilities as the completion criteria.

Written by the indexing model from the issue text.