Skip to content

Instantly share code, notes, and snippets.

@kimegede
Last active September 17, 2020 11:39
Show Gist options
  • Save kimegede/a532a2d2d516609176041b5d5f4ea297 to your computer and use it in GitHub Desktop.
Save kimegede/a532a2d2d516609176041b5d5f4ea297 to your computer and use it in GitHub Desktop.
GitHub Migration plan

GitHub Migration plan

BitBucket to GitHub

See Tech-rough-plan.md

TODO

  • Create a detailed plan
  • Add repositories to each section, to make it more verbose and clear.
    • Add Frontend repositories
    • Add Backend repositories
  • Communicate plan to developers

Migrate Clio’s repositores from BitBucket to GitHub.

Plan to migrate Frontend repositories

(Suggested deadline 6th October 2020)

  • Finalize GH actions for FE
  • Change build URL from static.clio.me to static-clio.me
  • Research Single or Multiple GH Actions (Files) (eg. CI & Deployment or CI+Deployment)
  • Import users into GH (Ensure devs have their keys etc.)
  • Import FE repositories (see frontend-repositories.md)
  • Deprecate imported BB repositories (Pipeline, Description ect.)
  • (Nice to have) Create guide to load different git config for work folder. (Add work email to GH & use that when commiting for work related repoes. (One email config for private use, one for work).
  • Update environment tool, to clone repositories from GH.
  • Document to cliodocs! + Communicate to devs

Plan to migrate Backend repositories

(Suggested deadline 3rd November 2020)

  • Zero, MyClio & Portals + (old) Clio UI
  • GitHub Actions: Zero, MyClio & Portals + (old) Clio UI
  • Update Jenkins Build jobs for Zero, MyClio & Portals + (old) Clio UI
  • Domain services

Plan to migrate rest + infrastructure repositories

(Deadline TBD)

Cleanup plan

  • Deprecate Verdaccio & use GH NPM Registry instead(?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment