jenkinsci / jenkinsci/durable-task-plugin

[JENKINS-58256] Improve Jenkins timeout messages for tracing their cause

Open
#458 0 comments 0 reactions 0 assignees View on GitHub
component:durable-task-plugin component:workflow-basic-steps-plugin imported-jira-issue pipeline priority:minor resolution:unresolved ux
Dominant language
Java
Stars
30
Forks
101
PR merge metrics
No merged PRs in 30d

Description

I blamed our vendor for misinterpreting a timeout option in their code.  They helpfully pointed out that their code did not generate the error messages "Cancelling nested steps due to timeout" and "Sending interrupt signal to process".

Searching for the source of these messages on Github, even after scoping to the jenkinsci organization, was a challenge.  For one, some recent branches did not carry these messages.

 

I thought that being explicit in the log messages would not hurt (I think of a progress we made since the Unix times with their say-not-a-single-word-more idea).  E.g., the messages can mention the "timeout" DSL clause that was the origin of it (with or without its location) and the amount of time that was allocated in that clause.

 

https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L405

 

https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/stable/src/main/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepExecution.java#L177

 

---
Originally reported by ilatypov, imported from: Improve Jenkins timeout messages for tracing their cause


  • status: Open
  • priority: Minor
  • component(s): durable-task-plugin, workflow-basic-steps-plugin
  • label(s): pipeline, user-experience
  • resolution: Unresolved
  • votes: 1
  • watchers: 2
  • imported: 2025-12-09

Raw content of original issue

I blamed our vendor for misinterpreting a timeout option in their code.  They helpfully pointed out that their code did not generate the error messages "Cancelling nested steps due to timeout" and "Sending interrupt signal to process".

Searching for the source of these messages on Github, even after scoping to the jenkinsci organization, was a challenge.  For one, some recent branches did not carry these messages.

 

I thought that being explicit in the log messages would not hurt (I think of a progress we made since the Unix times with their say-not-a-single-word-more idea).  E.g., the messages can mention the "timeout" DSL clause that was the origin of it (with or without its location) and the amount of time that was allocated in that clause.

 

https://github.com/jenkinsci/workflow-durable-task-step-plugin/blob/master/src/main/java/org/jenkinsci/plugins/workflow/steps/durable_task/DurableTaskStep.java#L405

 

https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/stable/src/main/java/org/jenkinsci/plugins/workflow/steps/TimeoutStepExecution.java#L177

 

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.