Folks; we're just moving into gitlab CI for doing build and assembly for our applications, and I am ended up with what seems a more complex question: Most of our applications (server sided as well as JavaFX client stuff) are maven based Java projects consisting of various interdependent modules. So far, we use per-module CI configurations to build (and subsequently, using mvn, deploy to the local maven repository) all these projects. This is pretty fine, but we want a more automated build/deployment chain to get applications automatically up and running in a testbed environment. So, this setup would require to ...
- ... define sort of "multi-module" builds including various git projects (and, even worse, dedicated tags of these), - ... manually or automatically build the whole project in the "right" order as soon as one of the sub projects had a commit, - ... in case of a successful build copy the artifacts over to some testbed environment and launching them over there (using passwordless ssh), I meanwhile figured out that at least the first thing can be done using gitlab CI build triggers, but I'm unsure about the rest. So to ask: Are there any recommended approaches or best-practise ways for doing things like these? Should I try getting this done using gitlab CI, or would I be better off adding some external tool such as jenkins? TIA and all the best, Kristian -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/6de54cda-bb5d-4ccd-b4f1-79d6cc3aee91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
