Skip to main content

Continuous Delivery

We use GitHub Actions for powering our automated delivery pipelines. Evolve includes several pipeline configurations that allow you to automatically deliver the platform from day one.

Overview​

Our continuous delivery setup leverages GitHub Actions to automate various aspects of the build, test, and deployment process across multiple cloud platforms (AWS, GCP, and Azure).

Key Components​

  1. Monorepo Structure: Our codebase is organized as a monorepo, which allows for easier management of dependencies and shared code across different parts of the platform.

  2. pnpm and Turborepo: We use pnpm as our package manager and Turborepo for optimizing builds in our monorepo structure.

  3. MACH Composer: We utilize MACH composer for managing and deploying our microservices architecture.

  4. Multi-Cloud Support: Our pipelines are designed to support deployments to AWS, GCP, and Azure, as well as specialized platforms like Vercel for frontend hosting.

Main Workflows​

CI/CD Pipeline​

Our main CI/CD pipeline (ci-cd.yaml) includes the following key steps:

  1. Validation: Checks for changes and validates the codebase.
  2. Testing: Runs unit tests and reports coverage.
  3. MACH Composer Validation: Validates configurations for different cloud environments.
  4. Storybook Testing: Runs tests for our Storybook components.
  5. Service-Specific Builds: Triggers builds for individual services based on changes.
  6. Test environment deployment: deployment of MACH composer configurations for AWS, Azure and GCP.

Preview Environments​

We use preview environments (preview-env-create.yaml) to deploy changes for pull requests, allowing for easier review and testing of changes before they're merged.

Storybook deployment​

A separate workflow (deploy-storybook.yaml) handles the deployment of Storybook to ensure the component library is always up-to-date.

Optimization Strategies​

  1. Caching: We implement caching for pnpm, Turborepo, and Terraform plugins to speed up builds.
  2. Conditional Job Execution: Jobs are only run when relevant files have changed, reducing unnecessary builds.
  3. Parallel Execution: Where possible, jobs are run in parallel to minimize overall pipeline duration.

Security Considerations​

  1. CODEOWNERS: We use a CODEOWNERS file to ensure the right teams review changes to critical parts of the codebase.
  2. Secrets Management: Sensitive information is stored as GitHub Secrets and accessed securely within workflows.
  3. Pull Request Validation: Automated checks (validate-pull-request.yaml) ensure pull requests meet standards before merging.

Continuous Improvement​

Our continuous delivery setup is constantly evolving. We regularly review and optimize our workflows to improve efficiency, reduce build times, and enhance the developer experience.

For more detailed information on optimizing deployments as your project grows, please refer to our Optimizing Deployments guide.