2015 IEEE/ACM 3rd International Workshop on Release Engineering (RELENG) (2015)
May 19, 2015 to May 19, 2015
This paper illustrates how Jenkins evolved from being a pure Continuous Integration Platform to a Continuous Delivery one, embracing the new design tendency where not only the build but also the release and the delivery process of the product is automated. In this scenario Jenkins becomes the orchestrator tool for all the teams/roles involved in the software lifecycle, thanks to which Development, Quality&Assurance and Operations teams can work closely together.Goal of this paper is not only to position Jenkins as hub for CD, but also introduce the challenges that still need to be solved in order to strengthen Jenkins' tracking capabilities.
Pipelines, Software, Automation, Time to market, Fingerprint recognition, Collaboration, Companies
V. Armenise, "Continuous Delivery with Jenkins: Jenkins Solutions to Implement Continuous Delivery," 2015 IEEE/ACM 3rd International Workshop on Release Engineering (RELENG), Florence, Italy, 2015, pp. 24-27.