-
New Feature
-
Resolution: Unresolved
-
Minor
Currently Jenkinsfile Runner does not support passing timeout to CLI. In Docker it may be worked around by timing out the Docker container, but in such case there is no way to have a graceful shutdown.
timeout() is not enough, because Jenkins may hang before Pipeline even starts.
Acceptance criteria:
- There is a soft and hard timeout options which may be set via CLI argument or passed via Environment variable (for Docker)
- If the option is set, timeout is applied to the execution
- Once the soft timeout happens, Jenkins instance termination is invoked (job termination and then instance shutdown)
- Once the hard timeout happens, Jenkins instance is forcefully aborted