On 6/26/25 09:01, Andreas A Loew -Extern wrote:
Hello Maven experts,having started to make a big legacy enterprise Java project (which previously used Jenkins) ready to build through GitLab CI/CD, I ran into the exact same problems as described here with regards to an obvious misfit between the concepts of GitLab Runner CI/CD and Maven:https://gitlab.com/gitlab-org/gitlab/-/issues/234078 <https:// gitlab.com/gitlab-org/gitlab/-/issues/234078>
Well, I can't address the core issue with GitLab (yet, it is an open source project and I might take a look to see if there is something to contribute to address the issue).
...snip...
Is there any established strategy in the Maven community on how to set up continuous builds/deployments using GitLab CI/CD? Or are we still – 5 years after the above issue has been opened with GitLab – lacking a “standard” solution here?
Take a look at the To Be Continuous Maven Pipeline templates. https://gitlab.com/to-be-continuous/mavenAs a contributor to the templates I can speak to their success in our enterprise. There are a number of strategies that the templates employ to reduce builds and more via the jobs in a set of unified stages that align to GitLab practices and dynamic pipelines.
See the contribution guide for hints "to borrow" https://to-be-continuous.gitlab.io/doc/dev/workflow/ And the Understanding and Usage guides may also be of help in your work https://to-be-continuous.gitlab.io/doc/understand/ https://to-be-continuous.gitlab.io/doc/usage/
Many thanks in advance for your kind help & best regards Andreas
HTH. Tim -- Timothy Stone ============= Some call me ... Tim. Husband, Father, Blogger, OSS, Architect, Wargamer, Home Brewer, and 🤓 Find me on GitLab | GitHub | Linked In | MeWe | GnuPG
OpenPGP_signature.asc
Description: OpenPGP digital signature
