Back
Question
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
- 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?
👋 Join WIP to participate
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) and sitemap validity
What do you use for that?
www.npmjs.com/package/broken-…
And for the sitemap it's a custom script to make sure that XML is valid, URLs are valid, etc.
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