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

Matrix parent build shouldn't consume an executor.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • matrix-project-plugin
    • None
    • Platform: All, OS: All

      Hi,

      On a multi-configuration project, I encounter a systematic deadlock because the
      parent job and one of its child are queued on the same node.

      The configuration matrix is as follows:
      [x] Build on multiple nodes
      [-] Individual nodes
      [x] APOLLON (apollon)
      [x] CHRONOS (chronos)
      [x] DEMETER (demeter)
      [ ] EOS (eos)
      [x] EROS (eros)
      [x] PAN (pan)
      [x] PONTOS (pontos)
      [ ] master (the master Hudson node)
      [+] Labels
      [ ] Axes

      Here is the console output:

      started
      Building remotely on PONTOS
      Triggering label=PAN
      Triggering label=APOLLON
      Triggering label=DEMETER
      Triggering label=PONTOS
      Triggering label=EROS
      Triggering label=CHRONOS

      All jobs except the ones on "PONTOS" successfully terminate.
      The parent job keeps executing, waiting for all its children termination, but it
      never stops as the child job supposed to run on "PONTOS" remains in the build queue.

      Enabling the master Hudson node has no effect. Its corresponding job also
      remains in the build queue.

      Thank you for reading.

      Regards,
      Regis.

          [JENKINS-936] Matrix parent build shouldn't consume an executor.

          Régis Desgroppes created issue -

          Right. The parent build needs to be run outside of the normal executors so that
          it can let child builds use that executor.

          In the mean time, a work around is to tie the parent build to somewhere where
          more executors are available.

          Kohsuke Kawaguchi added a comment - Right. The parent build needs to be run outside of the normal executors so that it can let child builds use that executor. In the mean time, a work around is to tie the parent build to somewhere where more executors are available.

          I don't see how to put in place the workaround you propose, in that the
          multi-project configuration page doesn't allow to tie the parent build to a
          dedicated node.

          Régis Desgroppes added a comment - I don't see how to put in place the workaround you propose, in that the multi-project configuration page doesn't allow to tie the parent build to a dedicated node.

              • Issue 961 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 961 has been marked as a duplicate of this issue. ***
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-961 [ JENKINS-961 ]

              • Issue 1432 has been marked as a duplicate of this issue. ***

          Kohsuke Kawaguchi added a comment - Issue 1432 has been marked as a duplicate of this issue. ***
          Kohsuke Kawaguchi made changes -
          Link New: This issue is duplicated by JENKINS-1432 [ JENKINS-1432 ]

          musilt2 added a comment -
              • Issue 1561 has been marked as a duplicate of this issue. ***

          musilt2 added a comment - Issue 1561 has been marked as a duplicate of this issue. ***
          musilt2 made changes -
          Link New: This issue is duplicated by JENKINS-1561 [ JENKINS-1561 ]

          musilt2 added a comment -

          what's the current status of this issue? any time-frame when the fix will be
          available?

          musilt2 added a comment - what's the current status of this issue? any time-frame when the fix will be available?

            rdesgroppes Régis Desgroppes
            rdesgroppes Régis Desgroppes
            Votes:
            24 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: