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

Unable to kill a job which is running

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      When I kill a running job in Jenkins at the very early stage of its build, it doesn't get killed and goes to a null state. I can't see that in the main console, but when I go to the job page, I see the job running. I am unable to kick off another build for the same job as it says that the job is already running. Please see the screenshot.
      The only way I have for now is to restart jenkins. It has been happening quite frequently in the past 2-3 days time. Please send me a resolution for this at the earliest, it is not easy to restart jenkins very often in a busy day.

      Thanks,
      Aswini

        Attachments

          Activity

          Hide
          batmat Baptiste Mathus added a comment -

          @Daniel I reopened before seing your comment, because the symptoms are exactly the same at first sight, and I didn't want to disseminate data onto different JIRA issues when it seemed to be the same one.
          But if needed I can still file a new one, and link to here.

          Show
          batmat Baptiste Mathus added a comment - @Daniel I reopened before seing your comment, because the symptoms are exactly the same at first sight, and I didn't want to disseminate data onto different JIRA issues when it seemed to be the same one. But if needed I can still file a new one, and link to here.
          Hide
          ozgurkaya_ist Ozgur Kaya added a comment -

          Disable the job and then enable the job.. You will see that all jobs has killed and not rerunning.

          Show
          ozgurkaya_ist Ozgur Kaya added a comment - Disable the job and then enable the job.. You will see that all jobs has killed and not rerunning.
          Hide
          danielbeck Daniel Beck added a comment -

          I didn't want to disseminate data onto different JIRA issues

          A good idea as long as it never misleads or contradicts. As soon as that happens it's a mess and you need to figure out what's going on. Since you can mark jobs as being related, this shouldn't be an issue.

          Show
          danielbeck Daniel Beck added a comment - I didn't want to disseminate data onto different JIRA issues A good idea as long as it never misleads or contradicts. As soon as that happens it's a mess and you need to figure out what's going on. Since you can mark jobs as being related, this shouldn't be an issue.
          Hide
          jglick Jesse Glick added a comment -

          Not sure why this got reassigned away from me. I committed the fix to the known issue. (If there are other issues with similar symptoms, they should be filed separately and linked.)

          Show
          jglick Jesse Glick added a comment - Not sure why this got reassigned away from me. I committed the fix to the known issue. (If there are other issues with similar symptoms, they should be filed separately and linked.)
          Hide
          sphalke Santosh Phalke added a comment -

          I observed the same issue in the Jenkins version. 1.625.3. The issue occurred in the Multi-configuration project job. In my case the issue appeared after changing the Job weight of the Multi-configuration project job to 2 from 1. The next build of the Multi-configuration project job were non responsive. The non-responsive build under the build history displayed the on hover message "Started Null ago, Estimated remaining time: null." Could trigger the next build after reverting the job weight to 1 and after enabling the job configuration option "Execute concurrent builds if necessary"

          Show
          sphalke Santosh Phalke added a comment - I observed the same issue in the Jenkins version. 1.625.3. The issue occurred in the Multi-configuration project job. In my case the issue appeared after changing the Job weight of the Multi-configuration project job to 2 from 1. The next build of the Multi-configuration project job were non responsive. The non-responsive build under the build history displayed the on hover message "Started Null ago, Estimated remaining time: null." Could trigger the next build after reverting the job weight to 1 and after enabling the job configuration option "Execute concurrent builds if necessary"

            People

            • Assignee:
              jglick Jesse Glick
              Reporter:
              aswini_r Aswini Rajasekaran
            • Votes:
              1 Vote for this issue
              Watchers:
              17 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: