-
Bug
-
Resolution: Done
-
Major
-
None
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...
- is duplicated by
-
JENKINS-10485 Subversion SCM Polling fails when using parameterized Repository URL
- Reopened
-
JENKINS-16116 subversion-plugin commit notification (1.43) does not consider global node properties in SCM URLs
- Resolved
-
JENKINS-10925 Parameter substitution on SVN Url does not work
- Closed
- is related to
-
JENKINS-23007 Subversion plugin 2.x cannot handle changelog computation with variables in SVN URLs
- Resolved
-
JENKINS-11592 NPE: Failed to record SCM polling
- Resolved
-
JENKINS-22922 Subversion : environment variables work only partially (got broken in 2.3 or prior, after 1.44)
- Resolved
-
JENKINS-22568 Subversion polling not work when Repository URL value is variable - E125002: Malformed URL '${SVN_REPO_VARIABLE}'
- Closed