Pipeline Improvements

2025 February

Ten-Minute Build
Rapid feedback loop enhances productivity and reduces integration issues.

Where are we?
-
Comprehensive test suite
- Unit and integration tests
- E2E tests which proved to catch real errors
- A good CI infrastructure where we can setup and run pipelines
Where are we?
- Avg. 80 mins to push a commit to dev env
- We wait for 8 hours in a day for the pipeline
- Avg. 28 mins to run all the tests
- In the last 3 months, we waited 3 days for 4 test files to run
- We spend at least 2 hours on UAT to run all the E2E tests in every deployment
- We don't have monitoring and alerting about CI issues and slowdowns
Where are we?

What we need?
&
Stabilisation
Speed Up
Goal #1
Trust in main
Goal #2
Max. 20 mins to push a commit to dev
Tracks
Track #1
Run all tests regularly
Stabilisation
Track #1
Run all tests regularly
Stabilisation
- Ensure supertest tests are running in nightly
- Ensure case study tests are running with the proper filters
- Run playwright tests in nightly
- Convert this job to run it regularly (eg. every hour)
- Notify teams when this job breaks
Track #2
Pipeline Monitoring
Stabilisation
Track #2
Pipeline Monitoring
Stabilisation
-
Push Job, Job Section, Test Suite,
Test File metrics to Datadog - Notify developer if a pipeline broke on their branch
- Notify developers if main pipeline broke
- Create dashboard for CI metrics in Datadog
Track #3
Better auto resource management for builds
Speed Up
Track #3
Better auto resource management for builds
Speed Up
- Faster autoscaler reaction to peak pipeline usage
- Analyse and improve CPU and memory usage of pipeline pods
Track #4
Speed up tests
Speed Up
Track #4
Speed up tests
Speed Up

Track #4
Speed up tests
Speed Up

Track #5
Speed up CI steps
Speed Up
Track #5
Speed up CI steps
Speed Up

Track #6
Speed up builds
Speed Up
Track #6
Speed up builds
Speed Up
- Try out rspack and/or vite to replace Webpack
Pipeline Improvements Days
By drawain
Pipeline Improvements Days
- 250