We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

How We Gained Observability Into Our CI/CD Pipeline

Formale Metadaten

Titel
How We Gained Observability Into Our CI/CD Pipeline
Untertitel
Using best of breed open source to monitor Jenkins
Serientitel
Anzahl der Teile
542
Autor
Lizenz
CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
We all know that observability is a must-have for operating systems in production. But we often neglect our own backyard - our software release process. That was our mistake, which led us to wasting time and energy in handling failures in the CI/CD pipeline, and made our Developer-on-Duty (DoD) shifts tedious. On this talk I’d like to share how we built effective observability into our CI/CD pipeline using intelligent data collection, dashboarding and alerting, to boost our response to failures and improve our quality of life on the way. This talk will give practical guidance on how to improve observability into your CI/CD pipeline. Whether you use Jenkins like we do, or other CI/CD tools, you’ll learn how to augment them and reach higher productivity.