• Type: Bug
• Resolution: Fixed
• Priority: Critical
• Component/s: external-workspace-manager-plugin
• Labels:

  • regression
• Environment:

  Jenkins 2.392 (also 2.390)
  pipeline 590.v6a_d052e5a_a_b_5
  Pipeline: Nodes and Processes Version 1234.v019404b_3832a

[JENKINS-70693] local workspace is used instead of external workspace

Roman Zwi created issue - 2023-02-27 09:15

Roman Zwi made changes - 2023-02-27 09:17

Description

Original: This happens since updating some plugins today (27.02.2023). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll)}} {{{    exwsPath=   pwd()}} {{    sh 'ls -la'}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] }}} {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

New: This happens since updating some plugins today (27.02.2023). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    }}{{exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

Roman Zwi made changes - 2023-02-27 09:17

Description

Original: This happens since updating some plugins today (27.02.2023). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    }}{{exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

New: This happens since updating some plugins today (27.02.2023). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{{}}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

Roman Zwi made changes - 2023-02-27 09:19

Description

Original: This happens since updating some plugins today (27.02.2023). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{{}}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

New: This happens since updating some plugins today (27.02.2023). I have a feeling that it might be related to [ JENKINS-70528 | https://issues.jenkins.io/browse/JENKINS-70528 ] (just a guess). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{{}}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

Roman Zwi made changes - 2023-02-27 09:20

Description

Original: This happens since updating some plugins today (27.02.2023). I have a feeling that it might be related to [ JENKINS-70528 | https://issues.jenkins.io/browse/JENKINS-70528 ] (just a guess). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{{}}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

New: This happens since updating some plugins today (27.02.2023). I have a feeling that it might be related to [JENKINS-70528|https://issues.jenkins.io/browse/JENKINS-70528] (just a guess). For testing I used following pipeline snippled (the job's name is "work_ServerCheck"): {{def exwsAll = exwsAllocate diskPoolId: 'ArchivedBuilds', path: "unmerged/work_ServerCheck"}} {{exws  (exwsAll) {}} {{    exwsPath=   pwd()    }} {{{}    println "exwsPath="+{}}}{{{}exwsPath{}}}{{{{}}{}}} {{    sh 'pwd'}} {{}}} This produces following output (I marked unexpected values {color:#de350b}red{color} - they used to be equal to the {color:#00875a}green{color} value in previous versions): {{10:02:42  {color:#00875a}Running in /media/Builds/unmerged/work_ServerCheck{color}}} {{10:02:42  [Pipeline] {}} {{10:02:42  [Pipeline] pwd}} {{10:02:42  [Pipeline] echo}} {{10:02:42  exwsPath={color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline] sh}} {{10:02:42  + pwd}} {{10:02:42  {color:#de350b}/rsync/JenkinsJobs/workspace/work_ServerCheck{color}}} {{10:02:42  [Pipeline]}} }  {{10:02:42  [Pipeline] // exws}} {{10:02:42  [Pipeline] echo}}

Roman Zwi made changes - 2023-02-27 09:23

Link

New: This issue is related to JENKINS-70528 [ JENKINS-70528 ]

Collapse comment: Alexandru Somai added a comment - 2023-03-01 13:17

Alexandru Somai added a comment - 2023-03-01 13:17

I haven't worked on this plugin for a very long time. It might take me a while to ramp-up with it + I'm quite busy lately, so I can't promise a fix any time soon.

If you think you can fix the issue, feel free to contribute. Thanks!

 

Expand comment: Alexandru Somai added a comment - 2023-03-01 13:17

Alexandru Somai added a comment - 2023-03-01 13:17 I haven't worked on this plugin for a very long time. It might take me a while to ramp-up with it + I'm quite busy lately, so I can't promise a fix any time soon. If you think you can fix the issue, feel free to contribute. Thanks!  

Collapse comment: Roman Zwi added a comment - 2023-03-02 09:40

Roman Zwi added a comment - 2023-03-02 09:40

I'm sorry, I don't have any knowledge about Jenkins plugin development.

But I managed to get my jobs running without using this plugin, so I disabled it.

Expand comment: Roman Zwi added a comment - 2023-03-02 09:40

Roman Zwi added a comment - 2023-03-02 09:40 I'm sorry, I don't have any knowledge about Jenkins plugin development. But I managed to get my jobs running without using this plugin, so I disabled it.

Collapse comment: Chris added a comment - 2023-03-02 21:40, Edited by Chris - 2023-03-03 12:31

Chris added a comment - 2023-03-02 21:40 - edited

I have exactly the same issue on my side respectively in my Jenkins environmet. We have also updated some plugins and the Jenkins from version 2.375.2 to 2.375.3 on February 27th and noticed same results as Roman. Strangely a rollback of all updated plugins and the Jenkins version back to 2.375.2 did not help either.

I was also able to reproduce the behavior by using the simple example from the GitHub README (same job and one node).

Expand comment: Chris added a comment - 2023-03-02 21:40, Edited by Chris - 2023-03-03 12:31

Chris added a comment - 2023-03-02 21:40 - edited I have exactly the same issue on my side respectively in my Jenkins environmet. We have also updated some plugins and the Jenkins from version 2.375.2 to 2.375.3 on February 27th and noticed same results as Roman. Strangely a rollback of all updated plugins and the Jenkins version back to 2.375.2 did not help either. I was also able to reproduce the behavior by using the simple example from the GitHub README (same job and one node).

Collapse comment: Ian added a comment - 2023-03-02 22:10

Ian added a comment - 2023-03-02 22:10

We also began experiencing this issue on feburary 17th. We use kubernetes and nodes are ephemeral, so pulling the repo on one node is supposed to go to a shared external workspace, but instead only clones to the node's workspace and so follow-on node workspaces are empty, which completely breaks our builds.

Expand comment: Ian added a comment - 2023-03-02 22:10

Ian added a comment - 2023-03-02 22:10 We also began experiencing this issue on feburary 17th. We use kubernetes and nodes are ephemeral, so pulling the repo on one node is supposed to go to a shared external workspace, but instead only clones to the node's workspace and so follow-on node workspaces are empty, which completely breaks our builds.

Load more newer events