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

Jobs stay queued forever if a node with the label is initially unavailable

    Details

    • Similar Issues:

      Description

      If a job sets a label and no node is available to run the job, the job just stays queued forever even if an appropriate node later becomes available.

      Is there some (groovy) way to "tickle" the job in the queue?

        Attachments

          Activity

          Hide
          cg Christian Goetze added a comment -

          I run that snippet I showed:

          jenkins.model.Jenkins.instance.labels.each { it.reset() }
          

          I'll check what trimLabels() does...

          Show
          cg Christian Goetze added a comment - I run that snippet I showed: jenkins.model.Jenkins.instance.labels.each { it.reset() } I'll check what trimLabels() does...
          Show
          cg Christian Goetze added a comment - I did check what it does: https://groups.google.com/forum/#!topic/jenkinsci-users/-4S9VYbocyA
          Hide
          danielbeck Daniel Beck added a comment -

          Well, that is embarassing

          Did the reset() work?

          Show
          danielbeck Daniel Beck added a comment - Well, that is embarassing Did the reset() work?
          Hide
          cg Christian Goetze added a comment -

          Actually, that's the point, it didn't appear to work.

          This being said, this isn't an urgent issue for me anymore, as I simply split the job into two separate jobs with their custom static label setting. Since I generate the jobs via the job DSL plugin, it's no big deal for me. The label assignment plugin failure mode makes it too risky to expose. I spend a whole night debugging the wrong job (the parent job trying to launch it) until I figured out it was the child job's label assignment plugin.

          Show
          cg Christian Goetze added a comment - Actually, that's the point, it didn't appear to work. This being said, this isn't an urgent issue for me anymore, as I simply split the job into two separate jobs with their custom static label setting. Since I generate the jobs via the job DSL plugin, it's no big deal for me. The label assignment plugin failure mode makes it too risky to expose. I spend a whole night debugging the wrong job (the parent job trying to launch it) until I figured out it was the child job's label assignment plugin.
          Hide
          ikedam ikedam added a comment -

          It looks an issue of how to change labels of nodes and not of groovy-label-assignment.

          Show
          ikedam ikedam added a comment - It looks an issue of how to change labels of nodes and not of groovy-label-assignment.

            People

            • Assignee:
              Unassigned
              Reporter:
              cg Christian Goetze
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: