Cannot access variables passed in Subversion URL


  • Cannot access SVN_URL and SVN_REVISION environment variables in my Subversion jobs


  • CloudBees Jenkins Enterprise


URLs in general are case-sensitive (with the exception of machine names). There may be URLs, or parts of URLs, where case doesn’t matter, but identifying these may not be easy. Users should always consider that URLs are case-sensitive.

Additionally, URLs used for Subversion repositories may not contain a double-slash //

Either of the above two conditions will typically result in the SVN_URL, SVN_REVISION variables to be passed into the job undefined (blank/empty values).

This URL will work successfully:

These two URLs typically will not work:

If you encounter other issues with Subversion URLs, it might be due to the way your build scripts are passing in variables to the end of the URL to append mainline or branch paths (e.g. /trunk or /branch/1.0). Please check case sensitivity of the URL, number of slashes or other characters, and ensure you’re running the latest version of the Subversion Plugin.

Have more questions?


  • 0
    Jcsouvignet Jcsouvignet


    I use jenkins with pipeline and subversion.

    I define a job on jenkinsfile in my subversion. The jenkinsfile deals with SVN_REVISION and SVN_URL.

    When I use an exact URL for "repository URL" in pipeline section of job, everything is good : SVN_REVISION and SVN_URL are set up.

    But if I use a parameter un URL, "https://****/svn/PRJ/tags/${MY_TAG}", SVN_REVISION and SVN_URL are null !

    How can I set this variables in my context ? 

    Thanks in advance



Please sign in to leave a comment.