Libération: Bringing Clarity and Standardization to CI/CD Pipelines

Company Profile

• Industry: Digital Media & News Publishing
• Scale: Multi-Team Engineering Organization
• Stack: GitLab CI/CD

What Changed with Plumber

Executive Summary

Libération, one of France’s leading digital news platforms, operates in a fast-paced environment where reliability and speed are essential.

As their engineering workflows evolved, CI/CD pipelines grew organically across projects. Over time, this led to increasing complexity, limited visibility, and inconsistent security practices.

To maintain agility while strengthening governance, Libération needed to standardize its CI/CD practices — without turning compliance into a manual burden.

We needed visibility first. Standardization came next.
Now our CI/CD pipelines are clear, consistent, and easier to maintain.

🎯 The Challenge: From Informal Pipelines to Shared Standards

Over the years, pipelines were built and adapted independently across teams.

This created several challenges:

• Lack of Visibility: No centralized view of pipeline structure or security posture
• Single Point of Knowledge: CI/CD governance relied primarily on one person
• No Standard Templates: Security components and best practices not consistently applied
• Manual Compliance Risk: No desire to ask teams to manually enforce governance

Libération needed to regain clarity before enforcing standards.

🔄 The Transformation: Visibility First, Standardization Second

Rather than imposing heavy governance, Libération focused on making pipelines observable and measurable.

The Old Way: Opaque and Person-Dependent

• 🔴 Limited Transparency: Difficult to know which pipelines met security expectations
• 🔴 Knowledge Concentration: CI/CD oversight largely handled by a single expert
• 🔴 Time-Consuming Maintenance: Each new project required custom configuration
• 🔴 No Scalable Governance Model: Standardization was hard to enforce and even harder to prove

The Plumber Way: Clear, Shared, Scalable

• 🟢 Centralized Visibility: Immediate overview of CI/CD posture across projects
• 🟢 Standard Components Enforced: Shared security and best-practice building blocks applied consistently
• 🟢 Reduced Maintenance Overhead: Faster pipeline creation with reusable, controlled templates
• 🟢 Team Accountability Without Friction: Developers contribute within a secure, standardized framework

💡 The Results

Libération transformed its CI/CD from an opaque, person-dependent setup into a visible, standardized delivery platform.

Today:

• Pipelines are monitored continuously.
• Security components are consistently applied.
• Teams can build faster using standardized templates.
• Governance no longer depends on manual reviews or a single individual.

CI/CD governance is no longer a hidden effort handled behind the scenes. It is a shared, scalable capability embedded in the organization.