Re:Monorepo or Multirepo? Role-Based Repositories
by peterwwillis on Saturday October 12, 2019 @08:40PM
(#21237405)
Each service has its own code directory, and there's one big "shared code" directory. When you build one service, you copy the shared code directory and the service-specific directory, move to the service-specific folder, run your build process. The artifact that results is that one service. Tagging becomes "<service>-<semver>" instead of just "<semver>". You may start out with deploying all the services every time (actually hugely simplifies building, testing, and deploying), but then later you break out the infra into separate services the same way as the builds.
Re:Monorepo or Multirepo? Role-Based Repositories
by smallnamespace on Saturday October 12, 2019 @07:03PM
(#21236975)
> Are we taking writing scripts which trigger further pipelines if they detect change in a path or its dependencies
Unless one enforces perfect one-to-one match between repo boundaries and deployments, this is also an issue with multirepos.
In practice, it's straightforward to write a short script that deploys a portion of a repo and have it trigger if its source subtree changes and then run it in your CI/CD environment.
So many questions, but they're all about identifying change and only deploying change...