Database Migration 2.12.11

[inodb]

Filing this as follow up to cBioPortal/cbioportal#8753. There were several issues with this roll out. Let's use next migration as an incentive to improve

• [ ] Improve documentation on a migration roll out (https://docs.cbioportal.org/4.-development/release-procedure#release-with-database-migration)
  • [ ] Several testing steps are not mentioned. For this release we set up a separate database for a week on AWS to run e2e tests against. We could also use the existing prod db to save some costs, but would be good to be explicit in docs on how to set it up.
  • [ ] Roll out docs don't specifically mention to open the PRs to the various pipelines first before migration. This is a good way to test whether the existing code in master breaks anything there
  • [ ] Run private pipelines importer against the migrated dev db, just to test if this repo is working
  • [ ] Only once all steps above are done we proceed with rollout
• [ ] Improve automation
  • [ ] we could always test latest master code of cbioportal in both pipelines repo and cmo-pipelines repo to see if there is anything currently in master that breaks compilation
  • [ ] an automated way of importing with pipelines repo to some migrated dev db would be ideal. At the moment this is a manual process

[inodb]

@averyniceday we are planning to roll this out in ~2 weeks. After Thanksgiving