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

Tied job tries to start on master with zero executors

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Blocker Blocker
    • maven-plugin
    • None
    • Hudson 1.342 and also in 1.351

      One of the jobs tries to start but it does not:
      In the 'All' view you don't see the job running.
      On the slaves you don't see the job running.
      As soon as you open the job, the next run is busy.
      If we open the console output there is nothing.

      When we open the time trendline of the job we see that it is executing on the master instead of the slave which it is tied to. See attachment.
      The job is stuck and the only way to fix it is to restart Hudson.

            Unassigned Unassigned
            cbos Cees Bos
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: