3 ms·
We use a change management process. Pretty much a jira ticket that outlines the change that needs to happen. Affected systems need to have someone review the pl
by sethammons 6y ago
We use a change management process. Pretty much a jira ticket that outlines the change that needs to happen. Affected systems need to have someone review the plan. It has a rollout and rollback process and instructions should be written in a way that anyone on the team could run it.
Ideally, all steps are scripts that have been code reviewed and tested in a staging or dev environment.
When it comes to DB migrations, the code is updated to work with the old and the new. The db migration happens and is ran by a script that is start/stoppable and has logs. The code is then updated to not need the old db stuffs.
- andriosr 6y agoNice! This is the best process I can think of. I’ve worked with this model. But then everybody in the team has access to run the scripts, right? In my case a few people had, and with scale they became bottlenecks