I’ve currently got a repository structure for a multi-module
gradle project that looks like:
I want to be able to kick off the builds for the deployables in parallel, but manage them independently.
By “independently” I mean, I don’t want to have to couple the deployments, so I can promote/rollback
deployable-a separately from
Since both of the deployables require the
core dependencies to be published prior, is this an advisable use case?
What I am planning to do is to have a pipeline that builds + publishes the core, and then calls build on each of the deployables, which will have their own pipeline(s).
Break apart mono repo into 1 deployable : 1 repo
Any feedback would be greatly appreciated!