2026-02-02, 16:50–17:15, B.1.0.14
How do you transform dozens of ansible network collections into predictable, “always-green” releases? We will share how the Ansible Networking team standardizes structure, testing, and release hygiene across collections, so users get fewer surprises and faster fixes. We will cover our CI gates (sanity/unit/integration), Galaxy readiness checks, branch strategy, and what “Done” means before publishing.
Managing a diverse set of Ansible Network collections from multiple vendors requires a disciplined approach to release management. This talk explores how the Ansible Networking team achieves consistent, reliable releases at scale. We will break down our CI gates, branching model, testing standards, and release criteria that keep our collections high-quality and production-ready.
We’ll take you through the key strategies and tools we use, including:
Best Practices: How to standardize development and release processes across multiple collections.
CI/CD Strategy: Leverage sanity, unit, and integration tests to ensure high-quality, stable releases.
Automation Hub Readiness: Define clear criteria for collection readiness before publishing.
Branch Strategy: Implement a disciplined branching model to simplify releases and development parallelism.
Definition of Done: How to ensure quality by establishing clear, measurable release criteria.
Outcomes-
1.quality workflows that ensure smooth, predictable releases for users and partners
2.Take home a repeatable release checklist you can copy
Associate Engineering Manager, Ansible Networking. Lead and manage the Ansible networking content engineering team at Red Hat.