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

Flyweight tasks only use one-off executor when they can be scheduled immediately

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • Linux/ubuntu14.04

      I have a fresh downloaded jenkins whitout plugins running and configured
      one dumb slave (slave1) connected via ssh+user/password.
      I set up a matrix project (a minimal example is attached) to build on
      slave1 and tie the parent to that slave (in advanced project settings)
      When
      1) the slave has only 1 executor
      2) the slave is configured to get online when needed ("take this slave on-line when in demand and off-line when idle")
      then the deadlock happens if the slave is offline when the project is triggered. The parent build wakes up the slave, but then stucks saying

      Configuration tst ยป slave1 is still in the queue: Waiting for next available executor on slave1

      Note that 1) and 2) are necessary to reproduce the bug. If the slave is
      accidentally online at build start, the project builds fine.

      This is maybe JENKINS-22502 but the minimalistic setup should allow
      to reproduce the bug easily.

        1. config.xml
          1 kB

            jglick Jesse Glick
            felixschwitzer felix schwitzer
            Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: