[JIRA] (JENKINS-60969) @libs pseudo-workspace collision due to branch name truncation

15 views
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Apr 24, 2020, 12:24:03 PM4/24/20
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / Bug JENKINS-60969
@libs pseudo-workspace collision due to branch name truncation
Change By: Jesse Glick
Summary: Unwanted job interaction if using global pipeline libraries @libs pseudo-workspace collision due to branch name truncation
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
Atlassian logo

soundcracker@gmail.com (JIRA)

unread,
Apr 24, 2020, 2:10:02 PM4/24/20
to jenkinsc...@googlegroups.com
Daniel Estermann updated an issue
Change By: Daniel Estermann
Attachment: screenshot-1.png

soundcracker@gmail.com (JIRA)

unread,
Apr 24, 2020, 2:11:02 PM4/24/20
to jenkinsc...@googlegroups.com
Daniel Estermann commented on Bug JENKINS-60969
 
Re: @libs pseudo-workspace collision due to branch name truncation

It doesn't seem to change anything, the folder names in ${JENKINS_HOME}/workspace look the same to me:

Without -Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED

With -Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED

soundcracker@gmail.com (JIRA)

unread,
Apr 24, 2020, 2:11:02 PM4/24/20
to jenkinsc...@googlegroups.com
Daniel Estermann updated an issue
Change By: Daniel Estermann
Attachment: screenshot-2.png

soundcracker@gmail.com (JIRA)

unread,
Apr 24, 2020, 2:12:02 PM4/24/20
to jenkinsc...@googlegroups.com
Daniel Estermann edited a comment on Bug JENKINS-60969
It doesn't seem to change anything, the folder names in {{${JENKINS_HOME}/workspace}} look the same to me:

*Without {{-Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED}}*
!screenshot-1.png|thumbnail!

*With {{-Djenkins.branch.WorkspaceLocatorImpl.MODE=ENABLED}}*
!screenshot-2.png|thumbnail!

[~swf] What do you think?

yves.schumann@ti8m.ch (JIRA)

unread,
Apr 24, 2020, 2:13:02 PM4/24/20
to jenkinsc...@googlegroups.com

Jesse Glick: What functionality is enabled, if this option is used?

jglick@cloudbees.com (JIRA)

unread,
Apr 24, 2020, 2:25:03 PM4/24/20
to jenkinsc...@googlegroups.com

The workspace management system introduced in JENKINS-2111 is enabled for all projects, not merely multibranch. I had thought this would affect the pseudo-workspaces used by workflow-cps-global-lib, but on closer inspection that seems to not be the issue. Possibly a bug in WorkspaceLocatorImpl. Would need to dig into a reproduction test case. Is /var/jenkins_home/workspace/workspaces.txt not tracking the various branch projects?

soundcracker@gmail.com (JIRA)

unread,
Apr 30, 2020, 3:36:03 AM4/30/20
to jenkinsc...@googlegroups.com
Daniel Estermann edited a comment on Bug JENKINS-60969
I've just checked {{/var/jenkins_home/workspace/workspaces.txt}} on my test instance. It contains indeed the following entries:

{noformat}
<path_to_project>/<branch>
<folder>
{noformat}

But IMHO it doesn't help against different jobs working on the same git folder.

soundcracker@gmail.com (JIRA)

unread,
Apr 30, 2020, 3:36:03 AM4/30/20
to jenkinsc...@googlegroups.com

I've just checked /var/jenkins_home/workspace/workspaces.txt on my test instance. It contains the following entries:

<path_to_project>/<branch>
<folder>

But IMHO it doesn't help against different jobs working on the same git folder.

jglick@cloudbees.com (JIRA)

unread,
Apr 30, 2020, 8:39:02 AM4/30/20
to jenkinsc...@googlegroups.com

Not sure offhand. Bug somewhere.

soundcracker@gmail.com (JIRA)

unread,
Apr 30, 2020, 8:46:03 AM4/30/20
to jenkinsc...@googlegroups.com

Jesse Glick May I hand over this issue to you?

jglick@cloudbees.com (JIRA)

unread,
Apr 30, 2020, 8:49:02 AM4/30/20
to jenkinsc...@googlegroups.com

No, I am not maintaining these plugins, sorry.
Reply all
Reply to author
Forward
0 new messages