CI/CD doesn't necessarily mean Jenkins
summary
Argues that CI/CD does not require Jenkins and shows a working alternative using Drone alongside mentions of Travis and CircleCI, claiming fewer UI interactions, faster runs and easier plugin development. Points out Jenkins workarounds like webhooks and Jenkinsfile but calls plugin development and Groovy painful. Demonstrates a Docker-based pipeline where plugins are containers, Drone is open source, container-native and uses a relational backend so you get measurable metrics, easy backup and restore, and a practical, functioning system.
AI-written summary · about
related talks
39mDrone CI vs Jenkins. Fight!
36mCI/CD BoF: Delivering Quality Quickly
52mBringing Continuous Delivery to Cloud-Scale with Jenkins, Docker and
34mContinuous Delivery with Jenkins Workflow
45mBuilding Your Continuous Delivery Toolkit
35mJenkins Scaling and Organization for an Efficient CI
34mContinuous Container Integration for Containers
13mEvolution of containers in continuous integration
