[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using a URL with an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{panel}{noformat}Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk]{noformat}{panel}This problem was resolved by updating the repository URL to use a lower-case hostname.
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
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ nopanel panel } {noformat} Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk]{ nopanel noformat } {panel} This problem was resolved by updating the repository URL to use a lower-case hostname.
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 i
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ code:title=error-message|borderStyle=solid nopanel }Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk]{ code nopanel }This problem was resolved by updating the repository URL to use a lower-case hostname.
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 e
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter updated an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Change By:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build.The Jenkins application log contains the following warning:{ { code:title=error-message|borderStyle=solid} Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVarsWARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known: [https://myserver.mydomain.com/svn/path/to/project/trunk] {code } } This problem was resolved by updating the repository URL to use a lower-case hostname.
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
[JIRA] (JENKINS-38943) SVN_REVISION environment variable not set when URL includes capitalized hostname
Title: Message Title
David Potter created an issue
Jenkins / JENKINS-38943
SVN_REVISION environment variable not set when URL includes capitalized hostname
Issue Type:
Bug
Assignee:
Unassigned
Components:
subversion-plugin
Created:
2016/Oct/12 11:43 PM
Environment:
Jenkins 2.7.4 running on CentOS 7 with Openjdk 1.8.0_91 Windows Build Agent running on Windows Server 2012 R2 (but I doubt the agent matters) Jenkins launched like this: {{export JENKINS_HOME=/opt/jenkins java -Dsvnkit.http.methods=Basic,NTLM,Negotiate,Digest -Djava.security.krb5.realm=mydomain.com -Djava.security.krb5.kdc=myhost.mydomain.com -Dsun.security.krb5.debug=false -Djavax.net.ssl.trustStore=cacerts -jar jenkins.war --httpPort=-1 --httpsPort=8080 --httpsKeyStore=/opt/jenkins/jenkins.jks --httpsKeyStorePassword=mypass &}}
Priority:
Minor
Reporter:
David Potter
When a project uses Subversion SCM and references the repository using an upper-case hostname, the SVN_REVISION environment variable is not set within the build. The Jenkins application log contains the following warning: {{Oct 12, 2016 1:19:24 PM hudson.scm.SubversionSCM buildEnvVars WARNING: no revision found corresponding to https://MYSERVER.mydomain.com/svn/path/to/project/trunk; known : https://myserver.mydomain.com/svn/path/to/project/trunk}} This problem was resolved by updating the repository URL to use a lower-case hostname.
