Replies: 3 comments 4 replies
-
|
Would definitely want the validation part, just to eliminate any confusion from pipeline writers who might wonder why their timeouts aren't being respected and end up submitting bug reports 😅 |
Beta Was this translation helpful? Give feedback.
-
|
I've created a PR for this. |
Beta Was this translation helpful? Give feedback.
-
|
I am curious, why not use OPA to achieve the same? One can have much better granularity, if required. Also, the pipeline operators would have very clear and detail messages. Personally, I am not convinced that it is Concourse job to impose these kind of restrictions... UPDATE: don't get me wrong. I understand the need for this very well. In our Concourse deployment, we impose the limit of 2h for all tasks.. but from experience, I can tell you, you will need a few exceptions for this. If you configure one global CONCOURSE_MAX_TASK_TIMEOUT, you will not be able to do so, with OPA you decide... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Concourse currently supports
CONCOURSE_DEFAULT_TASK_TIMEOUT, which provides default timeout for tasks that don't have a specified one. This is very useful for ensuring tasks don't run forever.However, there is no similar configuration for maximum allowed timeout for tasks. Users can set pipelines with big timeouts..
Proposal
Introduce a new configuration:
This property will define the maxium allowed timeout for a task, regardless of what is specified in the pipeline.
Expected Behaviour
If a task specifies a timeout larger than
CONCOURSE_MAX_TASK_TIMEOUT:CONCOURSE_MAX_TASK_TIMEOUTBeta Was this translation helpful? Give feedback.
All reactions