Our CD pipeline is rather disconnected from the CI one.. that is, from the deployment perspective, there’s no difference if the deployable artifact comes from a monorepo vs a regular repo. Once there is a built application, that becomes its own entity that we can work with (deploy to test environments, promote status for pre prod and prod etc, using a combination of automatic and manual verification depending on which application it is. So the monorepo thing becomes to detect and build only what is required/changed since some know previous change. (For this, we use a env var from the git plugin in jenkins telling us the git sha of the previous successfull build) (most of our applications are still in regular repos, so haven’t used the monorepo setup widely yet)