Hi Mark, I tried the same. but jenkins job is not passing the value to the parameter. My svn url is: http://KarthikDev-PC/svn/Sample/branches/SpringExample-${Branch-Version} i can see error message under svn url: "/branches/SpringExample-$Branch-Version" doesn't exist in the repository. Maybe you meant "/branches/SpringExample-1.0.0"?
Thanks, Karthik On Wednesday, 25 April 2012 23:07:42 UTC+5:30, mark_kendzior wrote: > > Linley, > Yes, you can do exactly what you said. I am doing that exact thing. > > Add a String pramater to the build job. In my case I use branch as > the parameter name. > In the SVN URL put something like this: > https://my-svn.com/branches/${branch} > > The SVN plugin will expand the ${branch} parameter for you. > > Mark > > On Apr 25, 6:52 am, Maven User <[email protected]> wrote: > > Have you tried global environment variables? > > > > Jenkins has so much intelligence built into polling, seems like a shame > to > > ditch that for some quicky hand-rolled script :-/ > > > > > > > > On Tuesday, April 24, 2012 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- Hide quoted text - > > > > - Show quoted text - -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cfb949a4-d6b3-4a54-b28f-86f88ab1a1d1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
