CI/CD doesn't necessarily mean Jenkins

And ignite talk given at DevOps Days TLV 2018, explaining the misuse of Jenkins, and why Drone (and others) can be many times a better solution.

Transcript

1. CI/CD doesn’t necessarily mean Jenkins
2. $ whoami Omer Hamerman ProdOps.io (formerly Devops IL) github.com/omerxx omer@prodops.io keybase.io/omerxx medium.com/@omerxx
3. Waste • Locate a job • Run the wrong one • Cancel • Find the right one and run it • But it fails.... • Check the logs • Manual changes are required
4. • Trigger by webhook or a command • Jenkins file • DSL But things are still missing - easy scale, plugins dev, self healing, servers are not stateless Improving the Jenkins process And seriously, groovy??
5. Drone to the rescue! (or CircleCI / TravisCI / GitlabCI / BB pipelines…..) Why Drone? Written in Golang, open source, super easy to set up, And basically just an awesome tool to work with
6. Container Native
7. Plugins for everything • Market place • Create your own
8. The power of controlling your own relational DB • Stateful decoupled system • Easy to backup • Easy restore • Measureable • Queryable
10. Bottom line Don’t fixate on the one thing everyone is using • Use what best suits you • Remove waste • Focus on innovation