Automatic triggering of downstream maven dependencies

I’m looking at replacing our existing Jenkins build system with GitLab’s CI/CD functionality. Overall it looks like we can do just about everything that we need, except for automatically triggering downstream maven dependencies. For example, say I have a utility project that gets used by several other projects. When I add the jobs for these projects in to Jenkins, it automatically figures out the dependencies, so that if I rebuild the utility project, the projects that are dependent on that project automatically get rebuilt as well. In GitLab it looks like I can trigger downstream projects, but I have to manually determine which projects to trigger, which would mean my utility project has to know about all the other projects that use it.

Is there a way to automatically trigger downstream dependency builds?

3 Likes

I’m looking for the same feature :blush:

We are slowing moving from Perforce + TeamCity to only GitLab. This is absolutely necessary for adoption.

Am I missing something or is it still impossible to do with gitlab?