3 years ago

Category: Kubernetes, Docker, github, gitlab

Many of the challenges developers run into with Continuous Integration (CI) pipelines stem from the fact that CI is siloed from the rest of the development process. Development environments use a completely separate (and often pared-down) configuration compared to CI, which builds, tests, and deploys in a more production-like setting.

First, the discrepancy between development and CI environments leads to hard-to-predict errors in CI.

Garden will know that in order to run integration tests for Service A, Service B also has to be running and up-to-date.

It’s also easy for Garden to spin up a working preview environment of your application with every CI run, which can be used during the QA and review process.