"A lot of people use Jenkins, it’s probably the most used CI tool for private use. It's robust, versatile and not at all complex to use. However it lacks job management usability at scale. When you have to deal with more than 10 jobs, it starts to be a boring and error prone task. What about using the same strategy that new CI tools are using? Like Travis for instance. Wouldn’t it be fantastic if we had a file in our code repository that Jenkins could recognise and execute jobs accordingly? I'm proposing a different way of using Jenkins. Using an open source tool called Jenkins Job Builder and by 'eating our own dog food', I will share a versionable, modular and easy way of managing your Jenkins jobs. This enables you to configure not only CI but also CD with just a YAML file."
http://mindera.com/blog/post/jenkins-a-la-travis
25. @jgbcravo @minderaswcraft@cfgmgmtcamp 2016
What is not so good…
Jenkins is not
a CD tool
http://cachet-software.com/cloudsidekick/velocity-blog/stretch-armstrong/
http://www.thatwasrad.com/product/stretch-armstrong/
26. @jgbcravo @minderaswcraft@cfgmgmtcamp 2016
… Future
- Jenkins 2.0
- Get a better flow radiator dashboard
- Get a artefact correlation manager
- Improve macros
- Run on scope containers