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

Matrix (multi-configuration) job ceates workspace@2 while not enable con-current build

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • matrix-project-plugin
    • None
    • Jenkins ver. 1.609.1 (upgraded from 1.580.3)
      Matrix Project Plugin: 1.6

      My matrix (multi-configuration) job is configured to
      "Run each configuration sequentially"
      and NOT "Execute concurrent builds if necessary".

      After upgrade Jenkins to 1.609.1 (from 1.580.3),
      the subsequent new build will still wait in the queue.
      But when the new build starts,
      the first configuration build will always be built under "workspace@2"
      instead of re-using the original "workspace".

      After first configuration build finished,
      the subsequent configuration build moves back to use the original "workspace".

      This issue is seen only when the build was staying in queue.
      If there's no existing build running,
      the first configuration build would start correctly under "workspace".

          [JENKINS-29661] Matrix (multi-configuration) job ceates workspace@2 while not enable con-current build

          Rick Liu created issue -
          Rick Liu made changes -
          Description Original: My matrix (multi-configuration) job is configure to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".
          New: My matrix (multi-configuration) job is configured to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".
          Daniel Beck made changes -
          Component/s New: matrix-project-plugin [ 18765 ]
          Component/s Original: core [ 15593 ]
          Rick Liu made changes -
          Description Original: My matrix (multi-configuration) job is configured to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".
          New: My matrix (multi-configuration) job is configured to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".

          After first configuration build finished,
          the subsequent configuration build moves back to use the original "workspace".
          Rick Liu made changes -
          Description Original: My matrix (multi-configuration) job is configured to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".

          After first configuration build finished,
          the subsequent configuration build moves back to use the original "workspace".
          New: My matrix (multi-configuration) job is configured to
          "Run each configuration sequentially"
          and NOT "Execute concurrent builds if necessary".

          After upgrade Jenkins to 1.609.1 (from 1.580.3),
          the subsequent new build will still wait in the queue.
          But when the new build starts,
          the first configuration build will always be built under "workspace@2"
          instead of re-using the original "workspace".

          After first configuration build finished,
          the subsequent configuration build moves back to use the original "workspace".

          This issue is seen only when the build was staying in queue.
          If there's no existing build running,
          the first configuration build would start correctly under "workspace".
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 164640 ] New: JNJira + In-Review [ 181663 ]

            Unassigned Unassigned
            totoroliu Rick Liu
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: