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

First build uses full project path as workspace instead of the shortened path as mapped in workspaces.txt

XMLWordPrintable

      As I understand it, workspaces.txt determines the mapping from the full project path to the shortened workspace name.

      This week, I noticed that some builds failed, because they tried to build into a workspace using the full project path instead of the shortened one. This mostly occurs for the first builds of a branch: later builds are ok (folder names are abbreviated for clarity) 

      ./jobs/C/jobs/S/jobs/L/branches/NewBranch/builds/1/log:Running on *MYNODE* in /home/jenkins/workspace/C/S/L/NewBranch <-- !!!
./jobs/C/jobs/S/jobs/L/branches/NewBranch/builds/2/log:Running on *MYNODE* in /home/jenkins/workspace/NewBranch_15
./jobs/C/jobs/S/jobs/L/branches/NewBranch/builds/3/log:Running on *MYNODE* in /home/jenkins/workspace/NewBranch_15

      Is this a regression, an issue with an upgrade path or caused by a corrupt workspaces.txt file?

       

            mjdetullio Matthew DeTullio
            kpop kpop
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: