to be continuous

The project's foundation was laid in 2019, leveraging GitLab CI's "include" feature. From the outset, the templates were designed as a honeypot, attracting newbies who wanted to set up their continuous integration without spending hours on GitLab CI, natively implementing all the killer-features offered by GitLab, and facilitating the adoption of modern tools and practices. The focus was on creating a system that not only streamlined development but also acted as a catalyst for the adoption of best practices in DevSecOps, consistent workflows, and efficient CI/CD pipelines.

In short, "to be continuous" modestly aims to lay the foundations for the standardization of CI/CD through semantic modeling, integrating Git workflows, environment management, the nature of tasks in a pipeline, and understanding the differences between CI and CD.

"to be continuous" is more than a collection of GitLab CI templates; it's a comprehensive project developed and maintained by DevOps and technology experts. This initiative streamlines the creation of state-of-the-art CI/CD pipelines, encompassing tasks such as building, testing, code analysis, infrastructure management, application deployment, and acceptance testing.

These templates are also accessible on Self-Managed GitLab instances through the gitlab-sync tool, ensuring your self-managed instance stays up-to-date.

Similar to Maven or Gradle, "to be continuous" follows conventions (default configurations) while remaining open to customization. Users can either overload configuration variables or overwrite YAML code to tailor it to their specific needs