[
https://issues.jenkins-ci.org/browse/JENKINS-10628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161813#comment-161813
]
Spike Hains commented on JENKINS-10628:
---------------------------------------
We absolutely love the speed, ease of use, and elegance of Jenkins, but not
being able to use SCM polling for our QA builds is quite an inconvenience. Is
there a workaround perhaps?
> SCM build trigger not working correctly with variables in SVN URL
> -----------------------------------------------------------------
>
> Key: JENKINS-10628
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10628
> Project: Jenkins
> Issue Type: Bug
> Components: subversion
> Affects Versions: current
> Reporter: creckord
> Assignee: sogabe
>
> I tried using variables in my SVN URL with Subversion plug-in 1.29, but now
> the SCM build trigger triggers a new build on every update check.
> I created two global variables in the Jenkins System Configuration:
> MYSVN_BASE=file:///home/svn/myproject
> MYSVN_BRANCH=trunk
> and in my build job I use
>
> $MYSVN_BASE/$MYSVN_BRANCH
> as the SVN URL and the SCM build trigger set to check every 15 minutes for
> updates.
> Despite a nasty "Invalid URL syntax" error marker below the URL field,
> checking out and building the project works fine. However, the log says:
> Started by an SCM change
> Updating file:///home/svn/myproject/trunk
> At revision 13360
> no revision recorded for $MYSVN_BASE/$MYSVN_BRANCH in the previous build
> And on any subsequent SCM check, the build is triggered with that same
> message...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
