Skip to content
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

Jenkins Pipeline Timeout Handling for Queue Wait Time #740

Open
Zhenye-Na opened this issue Jan 9, 2025 · 0 comments
Open

Jenkins Pipeline Timeout Handling for Queue Wait Time #740

Zhenye-Na opened this issue Jan 9, 2025 · 0 comments

Comments

@Zhenye-Na
Copy link

What feature do you want to see added?

Problem Description

When using lockable resources in Jenkins pipelines with a timeout set, there is a potential issue with pipelines timing out due to the queue wait time. Specifically:

  • There is a single lockable resource, e.g., LOCK_0.
  • Two pipelines, PIPELINE_A and PIPELINE_B, are competing to acquire LOCK_0.
  • Both pipelines have a timeout set to 12 hours.
  • PIPELINE_A acquires LOCK_0 and runs for 10 hours.
  • After PIPELINE_A finishes, PIPELINE_B starts, but it has been waiting in the queue for 10 hours.
  • PIPELINE_B needs more than 2 hours to complete, which exceeds the remaining timeout.

The issue here is that PIPELINE_B times out due to the queue wait time, even though its actual execution time would have been within the timeout period.

Proposed Solutions

  1. Is there a way to exclude the queue wait time from the timeout calculation?
  2. Are there any existing workarounds to handle this scenario?
  3. If not, could this be considered as a feature request?

Thanks!

Upstream changes

No response

Are you interested in contributing this feature?

No response

@Zhenye-Na Zhenye-Na changed the title Exclude queuing time from pipeline timeout Jenkins Pipeline Timeout Handling for Queue Wait Time Jan 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant