4 ms·
”It's also just a bit of an organizational nightmare to see 200+ jobs on the main screen” I never look at the main screen. You can create tabs that segment tho
by Someone 9y ago
”It's also just a bit of an organizational nightmare to see 200+ jobs on the main screen”
I never look at the main screen. You can create tabs that segment those 200 jobs. If your job names are consistent (as they should), you can do the segmenting by regular expression (I’m not sure whether creating tabs requires a plug-in)
As to doing (almost) the same thing for different projects: you can POST XML job definitions to the web interface, so if you have the rights to create jobs and to run code on your local system, you can script job creation. In my experience, that’s the way to keep job definitions consistent. To figure out what the XML to POST should look like, grab it from your browser by GETting job/jobname/config.xml (https://support.cloudbees.com/hc/en-us/articles/218353308-How-to-update-job-config-files-using-the-REST-API-and-cURL- https://support.cloudbees.com/hc/en-us/articles/218353308-Ho...)
Yes, that duplicates lots of stuff in the Jenkins job definitions, but you shouldn’t treat that as source, but as the output of your job creation scripts.
- tokenizerrr 9y agoIf you get to that point, check out the Job DSL plugin.
- Someone 9y agoI would have to convince the system administrator to install that plug-in. I also don’t like having to use yet another language (or two, counting Groovy and the Job DSL separately), but that, I could live with.