chicobento commented on issue #496:
URL: https://github.com/apache/maven-mvnd/issues/496#issuecomment-1007551519
On our CI pipelines, on a single build we launch mvn multiple times across
jenkins stages, eg: lint, test, integration test, javadocs and so on, so I
believe that we would benefit from mvnd on CI even though in that scenario, the
definition of long-running daemon might be not so long.
However, we have a problem similar to the @dcaillia , since the mvn calls
are made from containers launched by the jenkins host, so it would be really
nice if we had a way of redirecting the mvnd 'client' to reuse a daemon
launched by the host (or another container).
My initial idea is to perhaps spawn a mvnd 'daemon' container at the
beginning of the pipeline and then be able to redirect the other mvnd 'client'
container calls to reuse the daemon container.
Something like:
```
jenkins pipeline
- container 0: launch mvnd daemon
- container 1: mvnd clean
- container 2: mvnd package install
- container 3: mvnd test
- container 4: mvnd dependency:analyze
- ... and many other mvn plugins we run on our builds
```
Where container 1-4 calls would reuse the daemon launched by container 0.
Would that be possible ? Is there other strategy that we could benefit from
mvnd given our 'restriction' of launching mvn plugins on separate containers ?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
