[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Component/s: _unsorted Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198931.1556177657000.1690.1562231820062%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
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. Impact: "parent" is an often used folder name in Maven projects. 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 contentsh3. 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
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
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 contentsh3. 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
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Attachment: workspace-example-folders.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title 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 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
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 contentsh3. 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 404h3. 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)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title twolfart updated an issue Jenkins / JENKINS-57180 folder "parent" in workspace not browseable Change By: twolfart Attachment: workspace-click-on-parent.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57180) folder "parent" in workspace not browseable
Title: Message Title
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
[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title twolfart commented on JENKINS-12667 Re: No possibility to specify "Workspace Root Directory" for Slave node Thanks for the hint, pmv. For our usecase we decided to set the workspace for the affected jobs to avoid a global change of the workspace folder. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title twolfart commented on JENKINS-12667 Re: No possibility to specify "Workspace Root Directory" for Slave node As ridiculous as it may sound, but with Windows and some of its build tools still not being able to use more then 248 chars, saving a few digits with switching from "workspace" to "w" would be great. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40072) Multibranch creates multiple new directories
Title: Message Title twolfart commented on JENKINS-40072 Re: Multibranch creates multiple new directories Workaround in JENKINS-38706. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12462) Jenkins configuration page could be improved
Title: Message Title twolfart commented on JENKINS-12462 Re: Jenkins configuration page could be improved Another pain point are plugins that add lists of configurations. E.g. the "Publish over SSH"-Plugin adds lots of SSH Servers. 3 Servers (without "Advanced") fit on my screen, currently I have about 50 (numbers growing) - and this is only the list of one plugin. It would be a great improvement, if lists initially were not fully expanded with opened form items, but shown in a more compact variant where individual entries can be edited. Example: The plugin listing can fit 20 on a screen. A more sophisticated UX could enable sorting of the list entries depending on column, re-ordering, deleting from the list view, etc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title twolfart commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Downgrading to ssh agent plugin 1.8 worked for me, ssh credentials plugin is still at 1.11 (latest). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title twolfart updated an issue Jenkins / JENKINS-32120 With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Change By: twolfart Comment: Downgrading to ssh agent plugin 1.8 worked for me, ssh credentials plugin is still at 1.11 (latest). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27525) Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine
twolfart commented on JENKINS-27525 Invoke top-level Maven targets fails for Maven 3.3.1 on Windows machine The reasone for the change from .bat do .cmd is MNG-5776. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-25137) Allow installation of latest maven
twolfart created JENKINS-25137 Allow installation of latest maven Issue Type: New Feature Assignee: Unassigned Components: maven-plugin Created: 14/Oct/14 6:29 AM Description: It seems that there's a problem with the availability of the latest maven version in jenkins. Current available Version is 3.2.3 (website), Jenkins provides 3.2.2 Various tickets show that missing the latest version occurs from time to time: JENKINS-23826 JENKINS-22077 JENKINS-17220 JENKINS-8389 Is the reason maybe that the installers are taken from "archive" (which is very complete), and not from the official apache mirrors (which lists only the latest ones)? An improvement would be to have the possibility to use the latest maven version available. Project: Jenkins Priority: Major Reporter: twolfart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [publish-over-cifs] (JENKINS-23175) Add support for Credentials plugin supplied credentials
twolfart commented on JENKINS-23175 Add support for Credentials plugin supplied credentials Adding that feature would be very helpful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira] (JENKINS-23292) jira-plugin uses emails from jira
twolfart created JENKINS-23292 jira-plugin uses emails from jira Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jira Created: 03/Jun/14 1:50 PM Description: When sending an email, the jira-plugin provides an email adress from JIRA instead of the regular email adress combined from committer and the configured domain. if the username exists in jira, jenkins will use the email without any further notice that this happened the email adress is used even if the jira-account in question has no permission for the project being build (how should jenkins know?) the email adress is even used from disabled jira accounts (how should jenkins know?) this feature of the plugin can't be disabled This can lead to emails being sent to wrong recipients. Environment: Jenkins 1.558, Jira-Plugin 1.39, Email-ext plugin 2.37.2.2 Fix Versions: current Project: Jenkins Priority: Critical Reporter: twolfart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-20690) Subversion changes using Assembla
twolfart commented on JENKINS-20690 Subversion changes using Assembla I had the same effect, and could remove it with the same solution. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sonar] (JENKINS-16046) Sonar Plugin uses wrong maven repository
twolfart commented on JENKINS-16046 Sonar Plugin uses wrong maven repository I can confirm the fix. Thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17220) Add Maven 3.0.5 to the auto installer.
twolfart updated JENKINS-17220 Add Maven 3.0.5 to the auto installer. Change By: twolfart (15/Apr/13 2:05 PM) Description: http://jenkins.mirror.isppower.de/updates/updates/hudson.tasks.Maven.MavenInstaller.jsondoesntlistMaven3.0.5.Pleaseadd [ Maven3.0.5 |http://maven.apache.org/docs/3.0.5/release-notes.html] totheautoinstallerfilesforhudson.tasks.Maven.MavenInstaller. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-17220) Add Maven 3.0.5 to the auto installer.
twolfart assigned JENKINS-17220 to Kohsuke Kawaguchi Add Maven 3.0.5 to the auto installer. Change By: twolfart (15/Apr/13 2:05 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17220) Add Maven 3.0.5 to the auto installer.
twolfart updated JENKINS-17220 Add Maven 3.0.5 to the auto installer. Change By: twolfart (17/Mar/13 6:58 PM) Component/s: update-center This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17220) Add Maven 3.0.5 to the auto installer.
twolfart created JENKINS-17220 Add Maven 3.0.5 to the auto installer. Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: maven Created: 14/Mar/13 10:37 PM Description: http://jenkins.mirror.isppower.de/updates/updates/hudson.tasks.Maven.MavenInstaller.json doesn't list Maven 3.0.5. Please add Maven 3.0.5 to the auto installer files for hudson.tasks.Maven.MavenInstaller. Project: Jenkins Priority: Major Reporter: twolfart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16877) In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf
twolfart commented on JENKINS-16877 In Jenkins v1.480.3 encoding problems occur for XML api using a XPath function as leaf I have the same problem: After upgrading to 1.502 (from 1.49x) we can't detect the build status using: /lastBuild/api/xml?xpath=/mavenModuleSetBuild/result/text() It works without the xpath function, but provides the result-tag and not only the content: /lastBuild/api/xml?xpath=/mavenModuleSetBuild/result This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16046) Sonar Plugin uses wrong maven repository
twolfart
commented on JENKINS-16046
Sonar Plugin uses wrong maven repository
I'm currently using almost the same additional configuration (../../ instead of ${PWD}), but it didn't work for all projects with the global setting (some differ in paths).
Thank you Steve for pointing me to ${PWD}, that's more accurate then relative paths, and works for all of the projects.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16046) Sonar Plugin uses wrong maven repository
twolfart
created JENKINS-16046
Sonar Plugin uses wrong maven repository
Issue Type:
Bug
Affects Versions:
current
Assignee:
Sonar Team
Components:
sonar
Created:
05/Dec/12 1:18 PM
Description:
System Setup:
Jenkins is configured with Maven Project Configuration - Local Maven Repository set to Local to the executor to avoid concurrency problems with multiple maven builds on the same repository.
With this setting, the repositories on the machines are located at /path-to-jenkins/jenkins/maven-repositories/${EXECUTOR_NUMBER}/. With clean install, the artifacts are deployed in the executors repository.
This setup works fine for all the jobs we have.
On a local machine (and sonar configured), mvn sonar:sonar works fine.
Error:
When using the sonar plugin for the project, the project fails due to missing dependencies, although they have been created minutes ago.
Analysis:
In the build-log, I found that the sonar plugin executes the sonar call with this repository:
-Dmaven.repo.local=/path-to-jenkins/jenkins/workspace/project-name/.repository
This looks to me like sonar is using a project-based repository. I could not find a setting that lets sonar use the repository of the executor.
Expectation:
I expect the sonar plugin to automatically use the same maven repository that is used by the maven build step.
Environment:
* Jenkins 1.492, Sonar Plugin 2.0.1, Sonar 3.2
* Master (not building)
* Multiple nodes with multiple executors
* individual host for Sonar
* individual host for Sonars db
Project:
Jenkins
Priority:
Major
Reporter:
twolfart
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
