We cannot move fast enough with our development process
Beef up CI/CD machines. A possible short-term solution to buy us some time. But it is not infinitely scalable.
Current development, test, review, deployment cycle is very long
Try to find a way to optimize the processes. Maybe run things in parallel. This might get expensive.
Our cycle is very restrictive and blocks the developer from moving fast
Allow the process to be looser. Manage the risk somewhere else.
Over time the CI process was build by adding more into it, and we are failing the build if anything fails
Rethink the release process altogether. Remove redundant steps. Maybe we are doing things twice.
If | we remove all the processes from CI and leave only the CD related jobs |
---|---|
Then | the deployment cycle will become exactly as long as required for deployment |
But | Code quality may drop and we might miss bugs that would normally be caught in CI |
Anatoly Agulyansky
This is a great example how to apply the problem solving tools help to save time of a process. Good job.