#Migration strategy for multirepo project with submodules (Gitlab CI)

1 messages · Page 1 of 1 (latest)

silver jackal
#

The project I'm working on has a core repo with 10+ submodules. Each project has its own .gitlab-ci.yml. The submodules' pipelines build, test, and deploy packaes and the core one pulls them together in a few container images. I'm starting to remember all of the ways that Gitlab CI's rules & inclusion systems become too complicated, which is inspiring me to spike out Dagger (which I've only used for demo projects).

Would it be better to start from the submodules and work my way up? Or from the core project and go down?

Should I pull everything into one pipeline or continue to have separate projects be responsible for their own sub-pipelines? (I lean toward the former, but I'm not sure.)

Any other considerations for setting up Gitlab CI runners to work well with Dagger (beyond what's currently posted in the docs)? (Caching, etc.)

#

FWIW, I'm thinking of trying to move everything into one project eventually. I just don't know if that should be part of this, given that that's already going to be something I'll have to convince people of. But if those moves can be mutually supporting, maybe it's worth linking the efforts.

fierce snow
silver jackal
#

Cool, I'll take a look when I have more bandwidth. Is there a link for the recording yet? (Not seeing it on Youtube and the link I've found is for registering for future ones—which I'll definitely do.)

fierce snow
silver jackal
#

That was interesting, but it was from November and the presenter was someone else. 🙂

fierce snow