Does not have to, for example I usually do something like this: https://maveniverse.eu/blog/2024/09/07/very-simple-ci-setup/
True, this "carry over" idea works IF you are good with (built/installed) artifacts, as basically all I do is carry local repo from one job to another. For example, IT matrix runs like this, as explained. Thanks T On Thu, Jun 26, 2025 at 5:02 PM Andreas A Loew -Extern <andreas.a.loew-ext...@deutschebahn.com> wrote: > > Nils Breunese wrote: > > > Would it be an option to just do everything (build, test, code quality, > > etc.) in a single Maven execution in a single GitLab job? That way you > > wouldn’t need to pass any artifacts between multiple jobs. > > That's also the most simple I was thinking about - on the other hand, what > you lose with this approach is all advanced CI/CD functionality in GitLab > CI/CD, basically constraining it to a single-stage, single-job build...!? ☹ > > I still hope that there have been other approaches invented in the meantime... > > Thanks anyway, > Andreas > > -- > Andreas Loew > > externe Fachkraft im Auftrag der > Wavestone Germany AG > Leopoldstraße 28a, D-80802 München > > im Auftrag der > DB Energie GmbH (I.EFN 2) > Im Galluspark 25, D-60326 Frankfurt am Main > E-Mail: andreas.a.loew-ext...@deutschebahn.com > > ________________________________ > > Pflichtangaben anzeigen<https://www.deutschebahn.com/pflichtangaben/20250625> > > Nähere Informationen zur Datenverarbeitung im DB-Konzern finden Sie hier: > https://www.deutschebahn.com/de/konzern/datenschutz > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
