Over the last 10 years, continuous integration brought tangible improvements to the software delivery lifecycle with improvements that enabled adoption of agile delivery practices. The software industry is now progressing to the next maturity phase with continuous delivery. Jenkins has been established as a most widely used open source based automation tool. As currently in BC both public and government organizations experience with Jenkins grow, teams extend Jenkins beyond its original Continuous Integration focus with release and deployment which is next obvious automation points in the software delivery lifecycle.
There are additional factors that should be reviewed on the path to continuous delivery. These factors include componentizing the application under development, automating the entire pipeline and effectively managing contentious resources. Recently DevOps has been defined as an enterprise software development phrase used to mean a type of agile relationship between development and IT Operations. Its goal is to change and improve the relationship by advocating better communication and collaboration between the two business units. The latest incarnation of Jenkins has been positioned as a DevOps platform which include various value-added and enterprise-level features that are not easy to grasp for traditional Jenkins customers.
This talk first takes a holistic approach on Continuous Delivery challenges both on Premise and Cloud, secondly positioning Jenkins as an enabler on the Cloud specifically for cost effective SaaS and PaaS delivery.
The discussion includes best practices and how Jenkins bridges both sides of the development/operations divide, bringing both teams together and enabling collaboration.
Instructor, IT, Part Time Studies, University of British Columbia