Re: [Resend due to MS formatting Issues] GitLab CI/CD / GitLabRunner Pipelines: Stages versus Maven Lifecycle (GitLab issue #243078)

Tamás Cservenák <[email protected]> wrote:

> 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.

I’m trying to understand how this setup works, but I don’t really get it yet. Can you point out what the key is to making sure that the ‘Verify / Test’ jobs don’t build the artifacts that were already built in the ‘Verify / Build’ job again?

Looking at https://github.com/maveniverse/mima/actions/runs/15862328745/job/44722206227 for instance I see the following output:

[INFO] --- compiler:3.14.0:compile (default-compile) @ library ---
[INFO] Recompiling the module because of changed source code.
[INFO] Compiling 1 source file with javac [debug release 8] to target/classes

So it does like there is still compilation happening in this `Verify / Test` job?

Nils.