[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable

[twolfart@java.net (JIRA)]

twolfart created an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Issue Type: Bug Assignee: Unassigned Attachments: workspace-click-on-parent.PNG Components: _unsorted Created: 2019-04-25 07:34 Environment: 2.164.2, 2.169 on linux, others not checked Priority: Minor Reporter: twolfart A folder named "parent" in the workspace is not browseable for a pipeline job. Example pipeline: node { deleteDir() sh ("mkdir -p parent/foo") sh ("mkdir -p bar/parent") sh ("mkdir parent-foo") } Note: deleteDir() is only needed to re-run the job. It is not needed for the behaviour to appear. Impact: "parent" is an often used folder name in Maven projects. Works as expected (i.e. shows the folder): click on a job execution click on workspaces click on the listed workspace click on folder bar - shows contents click on folder bar/parent - shows contents click on folder parent-foo - shows contents Does not work as expected: click on a job execution click on workspaces click on the listed workspace click on folder parent - shows the parent node step click on folder parent/foo - results in 404 Workarounds use subfolder for project (i.e. project-name/parent) rename "parent" Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart

A folder named "parent" in the workspace is not browseable for a pipeline job. Example pipeline:

{code}

node {   deleteDir()   sh ("mkdir -p parent/foo")   sh ("mkdir -p bar/parent")   sh ("mkdir parent-foo") }

{code}

Note: {{deleteDir()}} is only needed to re-run the job. It is not needed for the behaviour to appear. Impact: "parent" is an often used folder name in Maven projects.

h3. Works as expected (i.e. shows the folder): * click on a job execution * click on workspaces * click on the listed workspace ** click on folder bar - shows contents ** click on folder bar/parent - shows contents ** click on folder parent-foo - shows contents h3. Does not work as expected: * click on a job execution * click on workspaces * click on the listed workspace ** click on folder parent - shows the parent node step !workspace-click-on-parent.PNG|thumbnail! ** click on folder parent/foo - results in 404 h3. Workarounds * use subfolder for project (i.e. project-name/parent) * rename "parent"

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart Attachment: workspace-click-on-parent.PNG

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart Attachment: workspace-click-on-parent-subfolder.PNG

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart

!workspace-click-on-parent-subfolder.PNG|thumbnail!

h3. Workarounds * use subfolder for project (i.e. project-name/parent) * rename "parent"

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart Attachment: workspace-example-folders.PNG

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart

A folder named "parent" in the workspace is not browseable for a pipeline job. Example pipeline: {code} node {   deleteDir()   sh ("mkdir -p parent/foo")   sh ("mkdir -p bar/parent")   sh ("mkdir parent-foo") } {code} Note: {{deleteDir()}} is only needed to re-run the job. It is not needed for the behaviour to appear.

This will create a workspace with the following folders: !workspace-example-folders.PNG!

Impact: "parent" is an often used folder name in Maven projects. h3. Works as expected (i.e. shows the folder): * click on a job execution * click on workspaces * click on the listed workspace ** click on folder bar - shows contents ** click on folder bar/parent - shows contents ** click on folder parent-foo - shows contents h3. Does not work as expected: * click on a job execution * click on workspaces * click on the listed workspace ** click on folder parent - shows the parent node step !workspace-click-on-parent.PNG|thumbnail! ** click on folder parent/foo - results in 404 !workspace-click-on-parent-subfolder.PNG|thumbnail! h3. Workarounds * use subfolder for project (i.e. project-name/parent) * rename "parent"

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart Component/s: core Component/s: _unsorted

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart

A folder named "parent" in the workspace is not browseable for a pipeline job.

Add Comment

[twolfart@java.net (JIRA)]

twolfart updated an issue

Jenkins / JENKINS-57180 folder "parent" in workspace not browseable

Change By: twolfart Component/s: _unsorted Component/s: core

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-57180

Re: folder "parent" in workspace not browseable I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace. Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated an issue

Jenkins / JENKINS-57180

folder "parent" in workspace not browseable

Change By: Mark Waite Component/s: pipeline Component/s: _unsorted

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-57180

Re: folder "parent" in workspace not browseable

I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace. Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin.

My test case job contained a pipeline definition like this: {noformat} node('!windows') {     stage('create dirs') {         deleteDir()         sh ("mkdir -p parent/foo && touch parent/foo/file-1")         sh ("mkdir -p bar/parent && touch bar/parent/file-2")         sh ("mkdir parent-foo    && touch parent-foo/file-3")         echo "OK URL is ${env.BUILD_URL}/execution/node/3/ws/"         echo "Odd URL is ${env.BUILD_URL}/execution/node/3/ws/parent/"         echo "Broken URL is ${env.BUILD_URL}/execution/node/3/ws/parent/foo"     } } {noformat} From the console output, clicking the "OK URL" works as expected.  Clicking the "Odd URL" causes a surprising result.  Clicking the "Broken URL" generates the 404 page not found.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite edited a comment on JENKINS-57180

Re: folder "parent" in workspace not browseable

I confirmed that the problem exists as described for pipeline jobs. Attempting to browse the workspace of a PIpeline job fails when attempting to navigate a directory named 'parent' at the root of the workspace. Same problem does not happen for Freestyle jobs. I've assigned the issue to a pipeline plugin. My test case job contained a pipeline definition like this: {noformat} node('!windows') {     stage('create dirs') {         deleteDir()

sh ("mkdir -p parent/foo")         sh ("mkdir -p bar/parent")         sh ("mkdir parent-foo")

echo "OK URL is ${env.BUILD_URL}/execution/node/3/ws/"         echo "Odd URL is ${env.BUILD_URL}/execution/node/3/ws/parent/"         echo "Broken URL is ${env.BUILD_URL}/execution/node/3/ws/parent/foo"     } } {noformat} From the console output, clicking the "OK URL" works as expected.  Clicking the "Odd URL" causes a surprising result.  Clicking the "Broken URL" generates the 404 page not found.

A test has also been added to [my docker-lfs repository|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-57180-pipeline-folder-named-parent-cannot-be-browsed/config.xml].

Add Comment