Back
Question
Asked

What steps are included in your CI pipeline you should have added sooner?

Our current CI process within a single Turborepo includes:

- Linting
- Type checking
- Running tests (backend and helper packages)
- Build
- Deployment

We’re considering adding Cypress tests and Lighthouse scores for key pages. What steps are included in your CI pipeline?


Auto-clear CDN Cloudflare cache after deployment (both in #crisp and #jomo ), to avoid cache issues

And on #crisp website, we have something that checks:
* dead links (very important)
* sitemap validity (even more important, if you build your own sitemap and don't notice it breaks, then you could loose months of SEO work)

I know some people like to do Lighthouse checks to see if changes and features improve or worsen the scores.

Depends on your setup, but I'd:
1. Add Infrastructure management: Terraform Plan / Apply, PR previews for plan and things like that.
2. Ensure caching + building without cache is oiled & greased!
3. Add meaningful k6 perf tests to get the sense of performance degradation

I'll suggest to add supply chain security checks and dependabot.

Yeah, that's a good one.

On top of enabling dependabot there must be a commitment to review and fix it's suggestions though! So many projects have it's PRs pending but there is no action at all.