Try this example, worked for me. Don't see why it can't be modified to use SVN:
https://namethattech.wordpress.com/2014/11/26/jenkins-git/ On Tuesday, April 24, 2012 at 9:46:27 AM UTC-4, Linley wrote: > > Hi, > > We have a SVN structure that consists of a main "parent" directory > which has sub-folders for each deployable project (which happen to be > Maven Java projects). Underneath these sub-folders are the SVN > branches, tags & trunk folders where the Maven Java project code > exists. For example: > > http://jira/svn/JiraProject [Main parent directory] > | > |--->ProjectA > | |--->branches > | |--->tags > | |--->trunk > | |--->maven-module > | |--->pom.xml > | > |--->ProjectB > | |--->branches > | |--->tags > | |--->trunk > | |--->maven-module > | |--->pom.xml > | > |--->etc... > > Currently, we have separate Jenkins jobs for each project (i.e. > Project A, Project B, etc) which checks out the code from the > Subversion trunk directory of the specific project (e.g. > http://jira/svn/JiraProject/ProjectA/trunk), builds it using a Maven > profile and triggers another Jenkins job to deploy to an environment. > > However, we are going to have a considerable number of these "child" > projects, so I was wondering if it is possible to have one "generic" > Jenkins build job rather than separate ones for each project (i.e. > ProjectA, ProjectB, etc)? > > If so, how do you parameterize the SVN "Repository URL" (e.g. > http://jira/svn/JiraProject/${project}/trunk, where ${project} can be > passed as a parameter at runtime)? > > Thanks -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b951d384-b29d-42bf-824c-02b946924f17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
