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

[jenkins-multijob-plugin] Multijob Freeze after first phase and all Executors are becoming Dead (!)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • multijob-plugin
    • None
    • Jenkins ver. 1.466.1
      Linux buildserver 2.6.18-164.11.1.el5PAE #1 SMP Wed Jan 6 13:43:57 EST 2010 i686 i686 i386 GNU/Linux

      I have set up a job that contains 2 Multijob phases, using the multijob plugin.
      I want to have two parameters for the job and pass them to both Multijob phases jobs.

      I will refer to the main Job as JobA.
      The first Multijob phase job as JobB and the second Multijob phase job as JobC.

      I have set up jobA that with 2 parameters.
      These parameters are passed jobB ('Current job parameters' is checked) - no problem, job ends with the correct parameters.
      But when the parameters are passed to JobC ('Current job parameters' is checked as well)- ALL available Build executors are turning into zombies with the status 'Dead ' with the exception:
      java.lang.NullPointerException
      at hudson.model.ParametersAction.getAssignedLabel(ParametersAction.java:126)
      at hudson.model.Queue$Item.getAssignedLabel(Queue.java:1265)
      at hudson.model.Node.canTake(Node.java:308)
      at hudson.model.Queue$JobOffer.canTake(Queue.java:210)
      at hudson.model.Queue.maintain(Queue.java:952)
      at hudson.model.Queue.pop(Queue.java:783)
      at hudson.model.Executor.grabJob(Executor.java:287)
      at hudson.model.Executor.run(Executor.java:208)

      At this stage:
      jobB has finished.
      jobC is pending start.
      jobA is waiting for JobC.

      Even if at this stage I go to the settings and enlarge the number of Executors, they immediately turn into zombies as well.

      Please advice.

            alex_nick Alex Nickolaevsky
            rotem Rotem G
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: