looking for resources, articles, or feedback on designing the CI/CD logic for a monorepo implementation

https://github.com/pantsbuild/pants/pull/5673 could be useful.

that’s a great start

now merged/published: https://www.pantsbuild.org/orgs.html

We have setup our ci/cd using jenkins with master/slave mode on openshift/kubernetes. Our CI runs unit/integration tests, creates docs, generates reports. Our CD process tracks the changed modules and creates/kicks of openshift pipeline. Lukasz can talk more. He did most of the work for us.

sounds pretty great... would be awesome to have a blogpost about that

seems to be working well with some gotchas for us

that would be great, esp relating the technical implementation to the organization develop/release process

Every deployable artifact ends up as a container using one of openshifts s2i (we have a builder image for that) and handles jars and pex to image, docker file, our airflow dags and spark jobs (on databricks) ends up on s3. We are in process of extending our CD process to handle that.

neat

We will try out best to come up with sth assuming legal is ok with it