Hello, I'm doing something similar to that. I have a parent project that polls SVN. When it detects a change, it performs it job then uses the parameterized trigger plugin to call on over 20 other jobs. I pass $SVN_URL_PREFIX as a parameter and use a shell to do checkouts. The parameter is defaulted to trunk in each child job.
Anthony On 2012-04-24, at 9:46 AM, 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
