Hi Mark, Does this means we don't have a documentation explaining the tags & attributes available?
regards Ramith LSF (www.opensource.lk) On Aug 20, 6:49 pm, Mark Waite <markwa...@yahoo.com> wrote: > I've used your technique of creating a similar job from the GUI and passing > that to the command line for multiple Jenkins releases. It works very well > for me. I prefer that technique because it also allows me to compare my > "archived" job definition (kept under source control for the project which it > builds) with the actual implementation in the running Jenkins system. > > Mark Waite > > > > > > > > >________________________________ > > From: Ramith Jayasinghe <ramithonl...@gmail.com> > >To: Jenkins Users <jenkinsci-users@googlegroups.com> > >Sent: Monday, August 20, 2012 7:20 AM > >Subject: Creating a new Job Programatically. > > >Hi Everyone, > >I'm trying to create a job in jenkins programmatically (using Remote > >Access API). By playing around and reading the documentation I found > >that I could do this by sending a xml document ( with a query > >parameter specifying the name of the job) with the configuration over > >http/Rest. > > >Therefore, Is there any document about this XML document? > > >For example, I want to create a job for application which resides on a > >SVN repo and build-able using maven 3. If we don't have documentation > >for options (tags and attributes) available for this XML fragment; I > >could create a similar job using the GUI and adapt my implementation > >based on the config.xml created for it. Would that be a good idea? > > >Regards, > >- Ramith > >LSF (www.opensource.lk)
