Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55295

Add support of Timeout option to Jenkinsfile Runner

    XMLWordPrintable

Details

    Description

      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

       

       

      Attachments

        Activity

          oleg_nenashev Oleg Nenashev created issue -
          oleg_nenashev Oleg Nenashev made changes -
          Field Original Value New Value
          Epic Link JENKINS-54342 [ 194995 ]
          vilacides Isa Vilacides made changes -
          Labels triaged
          egutierrez Evaristo Gutierrez made changes -
          Resolution Won't Fix [ 2 ]
          Status Open [ 1 ] Resolved [ 5 ]
          oleg_nenashev Oleg Nenashev made changes -
          Resolution Won't Fix [ 2 ]
          Status Resolved [ 5 ] Reopened [ 4 ]
          oleg_nenashev Oleg Nenashev made changes -
          Labels triaged
          oleg_nenashev Oleg Nenashev made changes -
          Description 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.

          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

           

           
          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

           

           
          oleg_nenashev Oleg Nenashev made changes -
          Epic Link JENKINS-54342 [ 194995 ]
          oleg_nenashev Oleg Nenashev made changes -
          Labels triaged

          People

            Unassigned Unassigned
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: