|
|
|
|
|
|
by mc4ndr3
1499 days ago
|
|
|
Where I've worked, we would use Jenkins for "Continuous Delivery" but then require upper management signoff for every single damn change. "We don't have time to test" -> Production poopfires -> "We need an out of band code review process" The faces on these people when one proposes deployment in terms of basic git triggers on protected branches. |
|
|
Sign-off would take 24 hrs to process, and the mysterious entity that signed off would have no context of our product or the changes, and no way to assess the risk.
Then, due to our lack of trusted regression testing, every damn change would take ~6 developers an entire work day to manually confirm that everything was working.
Why? We were measured on “number of tests.” The tech debt was too high to write quality tests before the next review, so we opted for quantity if we wanted promotion.
This was the hot path in a major (Fortune 10) financial company.