/ Build Automation: Reusing business logic wisely

Description

You're doing super-devops things as you support multiple product's pipelines from multiple teams. You're using a really wide toolchain includig CI servers like Jenkins, GitHub, AWS and ADO, but suddenly you get a business strategic request to move everything to a single CI server: Gitlab. Would you migrate all to the new CI server? or would you rather think that this is likely to happen again in the future and better do something more reusable? This is the case we recently faced and this is how we are trying to solve it. An approach to customise a Buid Automation System to reuse the business logic without the vendor lock-in effect. This session attempts to answer the following question: Is it possible to provide a unified software building solution that, while standardized, allows customisations, reduces maintenance cost, and greatly avoids vendor lock-in in CI platforms?

Session 🗣 Advanced ⭐⭐⭐ Track: DevOps, Kubernetes & Cloud (VMs, Docker, Security, ...)