login
Updated 07/25/2022
1

Speeding up CI/CD processes

Create a separate CI process only for the things which are not affecting functionality. Such as linters.
10
Alex Agulyansky
Jul 29 2020 3:54:27 pm
Use the exactly same package for prod deployment as for staging with proper config parameter.
10
Alex Agulyansky
Jul 29 2020 4:02:52 pm
Deploy first, then execute tests (or at least in parallel)
9
Alex Agulyansky
Jul 29 2020 3:57:00 pm
Execute the full build once a day or so, for monitoring
9
Alex Agulyansky
Jul 29 2020 3:57:39 pm
Add an additional requirement of PR: a report from the engineer which includes tests results, linters, etc...
7
Alex Agulyansky
Jul 29 2020 3:56:18 pm
Create a dashboard for periodic builds, so it's visible for everyone and everyone sees that there is a problem.
6
Alex Agulyansky
Jul 29 2020 4:09:07 pm
Use of feature flag for everything that we deliver, so things can be turned off whenever needed without affecting the user
5
Alex Agulyansky
Jul 29 2020 4:00:23 pm
Put the responsibility of code quality on the engineers
4
Alex Agulyansky
Jul 29 2020 3:47:35 pm
Execute the build only related to the changed of that build.
3
Alex Agulyansky
Jul 29 2020 3:49:33 pm
Within a separate steps of the build, combine the tasks that rely on the same preparation steps into one.
2
Alex Agulyansky
Jul 29 2020 3:50:19 pm
If a related test is failing, try to identify what feature was affected and how, and disable it temporarily until fixed.
1
Alex Agulyansky
Jul 29 2020 4:10:34 pm
Stop building all the sub projects together. We only need to build and check the sub-project that was affected
0
Alex Agulyansky
Jul 29 2020 3:51:15 pm