Do yourself a favor and look into the Job DSL plugin (https://github.com/jenkinsci/job-dsl-plugin). Managing Jenkins by hand is a hell.. so use the JobDSL and script it al together. And of course put the scripts in version control.
Most important JobDSL doc pages: - https://github.com/jenkinsci/job-dsl-plugin/blob/master/docs/Job-DSL-Commands.md - https://github.com/jenkinsci/job-dsl-plugin/blob/master/docs/Job-reference.md - https://github.com/jenkinsci/job-dsl-plugin/blob/master/docs/View-Reference.md Watch the following presentation to get an intro into the usages of the JobDSL plugin: - https://www.youtube.com/watch?v=Gyccyj6lA8k If you use Gradle for your JobDSL scripts repo, you can use my Gradle plugin to compile the DSL scripts to XML locally without having a Jenkins running. Handy for quick offline testing. But note, it does NO validation that it generated correct Jenkins XMLs, it only makes sure it is valid Groovy and that you used the JobDSL in a way that compiles. It uses the Jenkins JobDSL plugin code to compile the JobDSL, but the plugin itself also does no checks on it being valid Jenkins XML. My Gradle plugin can be found at: - https://github.com/pvdissel/gradle-jenkins-jobdsl If you want ideas on how to improve release flows, look into Continuous Delivery. Start by looking at: - http://continuousdelivery.com This is THE bible on Continuous Delivery. Enough stuff to read/watch available on there. Or if you want to start with the real basics, start with reading the following book: - http://martinfowler.com/books/duvall.html About the jobs structure.. It really depends how you're going to use Jenkins. Start simpel, and only add what is nessesary. The amount of jobs does not really matter. For your idea, with my team we currently have a Jenkins setup of 1 master with 3 slaves running a bit more then 1000 jobs. With multiple jobs for single apps/libraries/.., eg. CI, Deploy, DEV, TEST, ACC, PRO, etc. Almost all managed with JobDSL scripts. /Patrick On 10/29/2014 12:35 AM, Matt Klein wrote: > Thanks for the tips. I did a search and it appears build flow is a plugin. > I will check that out. > > Sounds like you are not 100% sure on the many project approach. Can you > elaborate a bit on the trades you considered for that approach vs. wrapping > many projects into a few jobs? > > Thanks again, > Matt > -- 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]. For more options, visit https://groups.google.com/d/optout.
