It's odd to find a place that doesn't have some kind of continuous integration/continuous delivery pipeline setup. Using CI/CD is one of the ways b...
For further actions, you may consider blocking this person and/or reporting abuse
While I appreciate a fast pipeline, it's just not possible in lot of cases. A glregionalized global service or onebox deploys expecting certain percent of traffic to validate changes, constant bake time before deploying to subsequent regions etc.
Rule of thumb is it should be fast but being fast isn't always critical.
Reliability > Speed
Good post! I'd second what Pedro mention about reliability. A good pipeline always produces the same output for a given input, with no oscillations in runtime. Intermittent failures or slowdowns cause intense frustration among developers.
Great summary of why ci/cd is needed!
With some API & e2e tests added as steps after deployments, any team member can basically deploy to Prod solo - or maybe even continuous deployment may be an option!
Very good points.
Two other things that I consider important (albeit pretty obvious) are:
it seems to me that the faster you want your CI/CD pipeline to deploy, the harder it gets to design and execute comprehensive testing. Maybe that's why the term "test in production" is popping up more frequently.
One central point should also be that code gets integrated to contral branch every day. Other points are great!