Slide 1

Slide 1 text

CI/CD doesn’t necessarily mean Jenkins

Slide 2

Slide 2 text

$ whoami Omer Hamerman ProdOps.io (formerly Devops IL) github.com/omerxx [email protected] keybase.io/omerxx medium.com/@omerxx

Slide 3

Slide 3 text

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

Slide 4

Slide 4 text

● 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??

Slide 5

Slide 5 text

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

Slide 6

Slide 6 text

Container Native

Slide 7

Slide 7 text

Plugins for everything ● Market place ● Create your own

Slide 8

Slide 8 text

The power of controlling your own relational DB ● Stateful decoupled system ● Easy to backup ● Easy restore ● Measureable ● Queryable

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

Bottom line Don’t fixate on the one thing everyone is using ● Use what best suits you ● Remove waste ● Focus on innovation