Re: manually created config.xml and plugin version numbers

2017-03-23 Thread Adam Levine
oups.com [ > jenkins...@googlegroups.com ] on behalf of Adam Levine [ > adam.l...@gmail.com ] > *Sent:* 20 March 2017 20:45 > *To:* Jenkins Users > *Subject:* manually created config.xml and plugin version numbers > > I've templated out some jobs, using gradle file copy/token

manually created config.xml and plugin version numbers

2017-03-20 Thread Adam Levine
I've templated out some jobs, using gradle file copy/token replacement and the cli create-job with my config.xml, and all is working fine. My question is on pieces that are plugins. ie 1 I already have a process in place to extract all the current plugins and versions and

Re: Createing job through CLI

2017-03-20 Thread Adam Levine
oops, didn't realize I posted on a 3yr old thread. On Wednesday, July 2, 2014 at 1:48:35 PM UTC-5, Mike Craig wrote: > > Hello, > > I am using the Jenkins CLI to pull down a list of 'template' jobs, search > and replace for our release version, then "create" a job using the job XML > which I hav

Re: Createing job through CLI

2017-03-20 Thread Adam Levine
Promoted build has a special subfolder, promotions, in the same dir as the config.xml. In the promotions directory, there is a directory for each promotion name/stage, each with a config.xml. It's quite possible those subfolders are not being copied over because they're a one-off. On Wedne