Details
-
Bug
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Won't Fix
-
Windows 2012 x64, Java 1.8, Jenkins 2.7.4, Pipeline: Multibranch 2.9, Pipeline: API 2.4, Linux Python
Description
Apparently after a recent update of plugins, our Multibranch Pipeline jobs started putting their workspaces in mangled locations. They used to be, for example, in D:\jenkins\cm-jenkins-09\my-pipline-job\my-branch-name and now they're like D:\jenkins\cm-jenkins-09\ine-job_my-banch-name-5P5URKHPJXWGGVIWDQOJBB3N7RJECAQJGFTDCVOPY3PABO7LNTIQ
There are several problems with this:
- They're difficult to read with all that garbage at the end, and the beginning of the name sometimes cut off
- They're not organized within the parent job like they used to be
- This is causing files within them to have extremely long paths such that Windows won't actually let us delete them (Jenkins, CMD, and Windows Explorer all fail to delete them)
Let me know if I can provide any other information to help solve this. This is a private Jenkins install so I can't point you to it.
Attachments
Issue Links
- duplicates
-
-
- Resolved
-
-
JENKINS-34564 Give the ability to choose how the multibranch subprojects will be named.
-
- Resolved
-
- is duplicated by
-
-
- Resolved
-
-
-
- Closed
-
-
-
- Resolved
-
- relates to
-
-
- Resolved
-
-
-
- Closed
-
-
JENKINS-52911 Higly voted critical issue JENKINS-38706 remains unassigned in JIRA
-
- Resolved
-
Activity
sascha bates
added a comment - My workaround for this was to define a jobName and then use the jobName in the workspace. The jobName var was also to account for feature branches and builds around several different microservices that might also have the same Jira id attached to them.
Our feature branch work is all short lived and named feature/jira-12345-some-description. Our services are named my-service-name. The below lines result in a 'my-service-name-jira-12345' workspace name. 99% of the time we don't need to look at workspaces anyway, but this makes the console log readable as well as making it possible to write directory cleanup patterns based on naming.
def jobName = JOB_NAME.replaceAll(/\/\w+%2F/,'-').toLowerCase()
ansiColor( 'xterm' ) {
timestamps {try {node() {
ws( "workspace/${jobName}" ) {
stage( 'Pull Github Repository' ) {
sascha bates
added a comment - My workaround for this was to define a jobName and then use the jobName in the workspace. The jobName var was also to account for feature branches and builds around several different microservices that might also have the same Jira id attached to them.
Our feature branch work is all short lived and named feature/jira-12345-some-description. Our services are named my-service-name. The below lines result in a 'my-service-name-jira-12345' workspace name. 99% of the time we don't need to look at workspaces anyway, but this makes the console log readable as well as making it possible to write directory cleanup patterns based on naming.
def jobName = JOB_NAME.replaceAll(/\/\w+%2F/,'-').toLowerCase()
ansiColor( 'xterm' ) {
timestamps { try { node() {
ws( "workspace/${jobName}" ) {
stage( 'Pull Github Repository' ) {
This issue became obsolete with the release of the fix of JENKINS-2111.
I am using Jenkins 2.150.2 version but still hitting this issue?
I also install short workspace plugins without any luck.
Is this truly fixed?
suemiao please do not reopen. If necessary, file a separate (but linked) bug report with complete steps to reproduce from scratch as well as FINE logs from jenkins.branch.WorkspaceLocatorImpl.
godskalk, I agree: less is certainly better, but name clashes should be avoided.