Lead Image © lightwise, 123RF.com
Zuul 3, a modern solution for CI/CD
Continuous Progress
Zuul 3 brings a new approach to the DevOps challenge. (For more on these important DevOps concepts, see the "CI and CD" box.) Whereas other CI/CD tools like Jenkins, Bamboo, or TeamCity focus on constant building and testing, Zuul's main design goal is to be a gating mechanism. In other words, as soon as a proposed change is verified and approved by a human, it can undergo final tests and be deployed automatically to the production environment. Such a system requires a lot of computing power, but Zuul has been proven reliable and highly scalable by its designers: the OpenStack community.
CI and CD
CI and CD are terms that pop up frequently in discussions of modern software development (Figure 1). CI stands for continuous integration , a practice that focuses on making releases easier to prepare. CD can mean either continuous delivery or continuous deployment , and although these practices have a lot in common, they also have significant differences [1].
Figure 1: Simply put, continuous integration is part of both continuous delivery and
Buy this article as PDF
(incl. VAT)
Buy ADMIN Magazine
US / Canada
UK / Australia
Related content
-
Sovereign Cloud Stack – a genuine alternative for Europe
The Sovereign Cloud Stack promises no less than liberation from the shackles of vendor tie-in. Cloud users who rely on this technology are free to choose their provider and switch, without further investment in training or financial penalty. -
The state of OpenStack in 2022
The unprecedented hype surrounding OpenStack 10 years ago changed to disillusionment, which has nevertheless had a positive effect: OpenStack is still evolving and is now mainly deployed where it actually makes sense to do so. -
When are Kubernetes and containers not a sensible solution?
As the major Linux distributors increasingly lean toward containers, many administrators have come to realize that containers are by no means a panacea for all their problems. -
Jenkins Configuration as Code
The move from Groovy scripts to Jenkins Configuration as Code simplifies the initialization of Jenkins and Jenkins plugins. -
Automated orchestration of a horizontally scalable build pipeline
A Jenkins build pipeline frees developers from repetitive manual build tasks by facilitating automation and provides broad traceability with continuous logging and feedback.
Subscribe to our ADMIN Newsletters
Subscribe to our Linux Newsletters
Find Linux and Open Source Jobs
Most Popular
Support Our Work
ADMIN content is made possible with support from readers like you. Please consider contributing when you've found an article to be beneficial.
