• Icon: New Feature New Feature
    • Resolution: Fixed
    • Icon: Minor Minor
    • cli
    • None

      Just like the safe-restart it could be nice if the CLI supported a safe-shutdown, it's not always you wish youre service to make a restart sometimes what you really what is to make a shutdown, do some maintanence and then start the service agian to make this steps automatic this CLI feature would be nice

          [JENKINS-6594] Hudson CLI should support safe-shutdown

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          core/src/main/java/jenkins/model/Jenkins.java
          http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c
          Log:
          [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c Log: [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          dogfood added a comment -

          Integrated in jenkins_main_trunk #1038
          [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          Kohsuke Kawaguchi : 7aad07c32e7d01df8792a69e99fb6f3e76f9206c
          Files :

          • changelog.html
          • core/src/main/java/jenkins/model/Jenkins.java

          dogfood added a comment - Integrated in jenkins_main_trunk #1038 [FIXED JENKINS-6594] added shutdown and safe-shutdown command Kohsuke Kawaguchi : 7aad07c32e7d01df8792a69e99fb6f3e76f9206c Files : changelog.html core/src/main/java/jenkins/model/Jenkins.java

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          core/src/main/java/jenkins/model/Jenkins.java
          http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c
          Log:
          [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c Log: [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          How about adding it to http console API as well? One can restart Jenkins via /safeRestart url and it would be very nice to be able to shutdown this way as well.

          Michał Minicki added a comment - How about adding it to http console API as well? One can restart Jenkins via /safeRestart url and it would be very nice to be able to shutdown this way as well.

          Code changed in jenkins
          User: Kohsuke Kawaguchi
          Path:
          changelog.html
          core/src/main/java/jenkins/model/Jenkins.java
          http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c
          Log:
          [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/jenkins/model/Jenkins.java http://jenkins-ci.org/commit/jenkins/7aad07c32e7d01df8792a69e99fb6f3e76f9206c Log: [FIXED JENKINS-6594] added shutdown and safe-shutdown command

          Hans Brolund added a comment -

          I tried this functionality in Jenkins ver. 1.432 and got some problem with a job (lets call it job A) that consists of a chain of builds triggered on other projects. Job A waits for all its builds to finnish. After calling safe-shutdown no more builds are allowed to start by Jenkins. This causes a deadlock since Jenkins waits for job A to finish but job A doesn't finish because one of it builds is not allowed to start.

          Is this a bug or should I configure job A in some other way?

          Hans Brolund added a comment - I tried this functionality in Jenkins ver. 1.432 and got some problem with a job (lets call it job A) that consists of a chain of builds triggered on other projects. Job A waits for all its builds to finnish. After calling safe-shutdown no more builds are allowed to start by Jenkins. This causes a deadlock since Jenkins waits for job A to finish but job A doesn't finish because one of it builds is not allowed to start. Is this a bug or should I configure job A in some other way?

            Unassigned Unassigned
            jes8 jes8
            Votes:
            1 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: