Jenkins + Docker = Continuous Improvement
2 likes1,814 views
The document discusses continuous improvement in software development using Jenkins and Docker, highlighting the benefits of efficiency, cost-effectiveness, and speed in CI/CD pipelines. It addresses key questions related to software development life cycle (SDLC) efficiency and the need for rapid change. Additionally, it outlines practical use cases for managing environments and integrating Docker with Jenkins for better workflow management.
Jenkins + Docker = Continuous Improvement
- 1. Jenkins + Docker Continuous Improvement
- 3. CloudBees • Jenkins Enterprise Company • Kohsuke CTO / Core committers • Red Hat / Linux = CloudBees / Jenkins • Subscriptions, Services, Training, Enterprise features • Growing / Hiring
- 8. Look in the mirror • How efficient is your SDLC? • Is there room for improvement? • How often do you address the gaps? • How quickly can you make a change ? • Is the system designed to support quick changes? • What’s your incentive to make a change?
- 10. Jenkins + Docker • Cheaper • Better Utilization • Ease of use • Faster • Provisioning • Integrated with Jenkins = Faster CD pipelines • Better (YMMV and you control it) • Faster feedback • Flexible - Change is easier
- 15. Use Cases • Manage Docker registry credentials centrally • Standardized environments • Support snow flake environments • Modular CD pipelines using Workflow • Container Dependency • Tracking containers
- 16. Demo