[GitHub] [maven-mvnd] ppalaga commented on issue #592: How to integrate mvnd in jenkins?

[GitBox <gi...@apache.org>]

ppalaga commented on issue #592:
URL: https://github.com/apache/maven-mvnd/issues/592#issuecomment-1367958957

   Using mvnd on a CI may or may not be a good idea depending on what you expect. 
   
   * Keeping a single daemon process up and running on CI worker nodes so that it can be used for multiple non-related builds might not be a good idea: it would perhaps be hard to implement and it might harm the reproducibility of the builds. mvnd is still relatively new and thus potentially buggy.
   * Using mvnd for multiple subsequent builds within the same CI job on the same worker node (such as first `mvnd install -DskipTests` in parallel and then `cd integration-tests && mvnd test` with or without `-1/--serial`) might work. Just make sure that the daemon process does not survive across your CI job boundaries. In this way you may benefit from better parallel builds (better logging and better CPU saturation compared to stock Maven) and from keeping the the daemon JVM warm which allows for faster execution on subsequent mvnd invocations.
   
   Given the above, feel free to try what is the best for you. 
   
   I tend to agree with @gnodet that implementing or advising about any given CI's configuration is out of scope here. You may want to contact your CI vendor for that.


-- 
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: issues-unsubscribe@maven.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org