Continuous Integration and Continuous Deployment
Who watches the watchers - a Jenkins journey
Look Ma, No Hands! Jenkins testability and monitoring
February 7, 2021
11:55 AM – 12:40 PM Add to calendar
11:55 AM – 12:40 PM Add to calendar
D.cicd
When Everything as Code converges to automate/test your processes, in this talk we would like to discuss further our journey and our vision to handle our automation programmatically.
When we started to use Jenkins at Elastic, there was already a team providing the service, similar to the SaaS you could see nowadays, so teams were encouraged to handle their automation using the Configuration as Code paradigm with the Jenkins Job Builder tool, but at a certain moment of time this particular approach didn’t scale much, and that’s when we started to think about a more robust, testable and automated CI/CD ecosystem.
Then our journey started by applying the below principles and practices:
Everything as Code
Everything is Tested
Documentation as Code
Functional testing
Continuous Improvement
Continuous Deployment
All the above concepts are the ones that helped us in this journey and that’s the reason for this talk to share our experience and vision. Besides gathering from you your opinions and feedback.
Additional information
| Type | devroom |
|---|
More sessions
| 2/7/21 |
Introduction of the CI/CD devroom
|
| 2/7/21 |
The emergence of virtualization, containers, and cloud native has resulted in tremendous advances in enabling organizations to develop new services and make them available to end users. In addition, new paradigms such as Continuous Integration (CI) and Continuous Delivery (CD) allow organisations to do this much faster than before, empowering them to go to market ahead of the competition. Despite its many advantages, the CI/CD ecosystem has its challenges. This session will discuss issues ...
|
| 2/7/21 |
Three phrases keep popping up when talking about modern workflows and development and deployment techniques; CD, GitOps, and progressive delivery.
|
| 2/7/21 |
Continuous integration and deployment (CI/CD) system are hardly ever ceaseless as the name would suggest; they do aim though to follow changes in code, configurations and versions. They often achieve that by both handling and generating events. For instance, a CD system receives an event that describes a new version of an application, and it runs a workflow in response. When the workflow starts or when it reaches completion, the CD system generates events for the benefit of other processes that ...
|
| 2/7/21 |
Recently, the MariaDB Foundation has been developing a new continuous integration framework for the MariaDB Server. The goal of buildbot.mariadb.org is to ensure that each change is properly tested on all supported platforms and operating systems. Our new CI uses almost exclusively latent workers, more exactly Docker latent workers. In this talk, I will present a main overview of the CI infrastructure, the advantages of using latent workers and talk about the challenges that we encountered along ...
|
| 2/7/21 |
Kubernetes, GitOps, and Infrastructure as Code are as powerful as they are popular and seem like the perfect match. Consequently, using Terraform to maintain Kubernetes clusters and resources is a very common use-case. And it requires careful integration of many moving parts, from Terraform providers and modules, to CI/CD pipelines and triggers. However, despite this being such a popular use-case, teams previously had no alternative than writing everything from scratch. On the software ...
|
| 2/7/21 |
The Kubernetes tooling landscape is littered with template based solutions to deal with all the YAML needed to get things done. Kuberig takes a different approach that developers will love! No need to learn another template language or tool. With Kuberig you define your resources using Kotlin code and deploy them by executing Gradle tasks. Simple.
|
