Aftermath: Failed Update 1.23
What happened
The update has failed, because the production server was still running Node v7. A rollback wasn't possible, because the build of the version before failed with Node 7, too. But we've been successful re-deploying the last pipeline.
What comes next
We should set a schedule when to update to the next Node LTS version (v10) in order to release the new App version shortly after that.
Steps to prevent such situations
1. Backup while updating
In order to make a fast rollback possible we should create an archive of the current server files before we upload a new release. This could be added to the deploy.sh
.
2. Define a required Node update in milestones
We should add the information about an update to the current milestone when the development server needed to be updated, because a newer Node version is required. This way it can be planned to update the production server before the release.
3. Distribute the right to update node
We should talk about, who should be able to update node besides Doug, maybe.