https://www.exygen.fr/en/tags/docker/Recent content in Docker on ExygenHugo -- gohugo.ioenExygenMon, 15 Jun 2026 00:00:00 +0000https://www.exygen.fr/en/blog/2026/06/15/selfhostedcicd/Mon, 15 Jun 2026 00:00:00 +0000https://www.exygen.fr/en/blog/2026/06/15/selfhostedcicd/ <p>Running a dozen repositories and about twenty applications, libraries and websites quickly raises a simple but structural question: do you industrialize the build and deployment chain, or keep patching it together repo by repo? The choice made here was to design a self-hosted CI/CD platform, treated as a proper internal product — with its own design rules, auto-generated documentation, and its own lifecycle.</p> <p>An important clarification before going further: this platform isn't meant to be &quot;better&quot; than an established SaaS offering (GitHub Actions, GitLab CI, Bitbucket Pipelines...) in terms of features or operational comfort. It's a <strong>sovereignty</strong> choice — keeping code, artifacts and build data under your own roof — accepted with its costs, and relevant above all for an organization that already has the in-house IT capacity to operate it over time. That point is developed further below.</p>