[JIRA] (JENKINS-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title Stephen Morley commented on JENKINS-54654 Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths Jesse Glick that might explain why the setting was not updated but why is it not valid to reference a directory outside of the JENKINS_HOME. Personally I don't like keeping active data sets in the "Program Files (x86)" directory. This has worked for over 5 years now and suddenly it fails. (Turns out we also have a problem with some utility which is not working with the spaces in the path name so our builds are broken using this form but without it Jenkins just chokes). 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-54654) A recent update breaks builds by escaping slashes to percent signs in workspace paths
Title: Message Title
Stephen Morley commented on JENKINS-54654
Re: A recent update breaks builds by escaping slashes to percent signs in workspace paths
This problem appeared after I did an upgrade. I tried to restore to previous version and plugins but problem persisted. I enabled a log as noted above and found a message: JENKINS-2111 path sanitization ineffective when using legacy workspace root directory c:\JenkinsWorkspace\${ITEM_FULLNAME}; switch to ${JENKINS_HOME}/workspace/${ITEM_FULLNAME} so I did and its working now! This did move to a new workplace so all the directories are now so I don't know if that fixed it or the form of the path. Note the slashes were reversed. Before this Jenkins was creating a working directory simply with the first part of the name , e.g. QA/V2018 became QA
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-38664) bitbucket source plugin fails with bad URL
Title: Message Title Stephen Morley commented on JENKINS-38664 Re: bitbucket source plugin fails with bad URL Confirmed. After I changed the Jenkins URL to the IP address the problem went away. We're in a small shop so I don't have a domain name I can add to the normal URL. 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.
