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

Build creates second workspace@2 for non-concurrent build configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Duplicate
    • Component/s: core, matrix-project-plugin
    • Labels:
      None
    • Environment:
      OS: Ubuntu 12.04 64-bit
      Jenkins: 1.609.1 (upgraded from 1.580.3)
      disk-usage plugin: 0.25 (upgraded from 0.24)
      Matrix Project Plugin: 1.6 (upgraded from 1.4.1)
    • Similar Issues:
    • Released As:
      Jenkins Core 2.136

      Description

      I didn't have this issue when I was using ver 1.580.3.
      After upgrading Jenkins ver 1.609.1 (together with other Jenkins plugins update),
      I started to see this issue.

      My jenkins job is using multi-config project type (aka Matrix project),
      and has 3 variants.
      I didn't set to be run concurrently,
      so the 3 variants will start the build one by one.

      In the previous version 1.580.3,
      it will reuse the same workspace folder for all of 3 variant builds.

      In the new version 1.609.1,
      when multiple jobs are triggerd,
      I can see sometimes the first variant build of the second job
      will start to create and use workspace@2
      instead of re-using original worksapce.

      Note:
      I'm also using disk-usage plugin.
      At the end of build,
      it will trigger that plugin to calculate workspace disk space.
      My work space tends to be large and sometimes it take several minutes to finish.

      I suspect it's that disk-usage plugin still occupying the original worksapce,
      but the second job in queue starts earlier,
      so it creates workspace@2 for the first variable build.

      From workspace@2,
      I always see only one variant only under AXIS folder.

        Attachments

          Issue Links

            Activity

            Hide
            dnusbaum Devin Nusbaum added a comment -

            JENKINS-41127, which may have been the root cause of this issue, was just fixed in Jenkins 2.136. Does anyone have a test environment in which they can consistently reproduce this issue? If so, it would be great if you could test whether this problem still occurs in Jenkins 2.136 or newer.

            Show
            dnusbaum Devin Nusbaum added a comment - JENKINS-41127 , which may have been the root cause of this issue, was just fixed in Jenkins 2.136 . Does anyone have a test environment in which they can consistently reproduce this issue? If so, it would be great if you could test whether this problem still occurs in Jenkins 2.136 or newer.
            Hide
            dnusbaum Devin Nusbaum added a comment - - edited

            Since I have not heard back either way, I am going to go ahead and close this issue because at least one way it could happen was fixed in Jenkins 2.136. Please feel free to reopen the issue if you are still seeing it in Jenkins 2.136 or newer.

            Show
            dnusbaum Devin Nusbaum added a comment - - edited Since I have not heard back either way, I am going to go ahead and close this issue because at least one way it could happen was fixed in Jenkins 2.136. Please feel free to reopen the issue if you are still seeing it in Jenkins 2.136 or newer.
            Hide
            openjenkins J S added a comment -

            I have the same problem at Jenkins Version : 2.121.3

            Show
            openjenkins J S added a comment - I have the same problem at Jenkins Version : 2.121.3
            Hide
            openjenkins J S added a comment -

            I still have the same problem on Jenkins Version 2.121.3 LTS .

            On my Slave i get the Folder @2 that are very big.

            Show
            openjenkins J S added a comment - I still have the same problem on Jenkins Version 2.121.3 LTS . On my Slave i get the Folder @2 that are very big.
            Hide
            dnusbaum Devin Nusbaum added a comment - - edited

            J S The change I made to fix JENKINS-41127 is in 2.136, and it was not backported to the 2.121.x LTS line (It is in the 2.138.x LTS line). Please only reopen the issue if you are seeing it in 2.136 or newer (unless you have additional information that leads you to believe it is distinct from JENKINS-41127, such as seeing the issue for something other than a pipeline or matrix job, and please include any relevant info if that is the case).

            Show
            dnusbaum Devin Nusbaum added a comment - - edited J S The change I made to fix JENKINS-41127 is in 2.136, and it was not backported to the 2.121.x LTS line (It is in the 2.138.x LTS line). Please only reopen the issue if you are seeing it in 2.136 or newer (unless you have additional information that leads you to believe it is distinct from JENKINS-41127 , such as seeing the issue for something other than a pipeline or matrix job, and please include any relevant info if that is the case).

              People

              • Assignee:
                dnusbaum Devin Nusbaum
                Reporter:
                totoroliu Rick Liu
              • Votes:
                4 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: