[JIRA] [core] (JENKINS-28123) Jobs stay queued forever if a node with the label is initially unavailable

Sat, 02 May 2015 19:59:55 -0700

ikedam commented on Bug JENKINS-28123

Anyway, I could not reproduce the problem with Jenkins 1.596.2

Configuration:

  • Create a node named "slave1".
  • Create a free style project "test".
    • Check "Groovy script to restrict where this project can be run"
      noformat
      return "target";
      noformat

Test1:

  • Steps
    1. Set the label of "slave1" to "xtarget".
    2. Run a build of "test". The build is queued.
    3. Change the label of "slave1" to "target".
  • Result
    • The build starts on "slave1".

Test2:

  • Steps
    1. Set the label of "slave1" to "target".
    2. Make "slave1" offline.
    3. Run a build of "test". The build is queued.
    4. Make "slave1" online.
  • Result
    • The build starts on "slave1".

Test3:

  • Steps
    1. Set the label of "slave1" to "target".
    2. Disconnect "slave1".
    3. Run a build of "test". The build is queued.
    4. Connect "slave1".
  • Result
    • The build starts on "slave1".
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to