Usage of mvnd on Jenkins for parallel builds
- Dominant language
- Java
- Stars
- 3.5k
- Forks
- 250
- Avg merge
- 16h 22m
- Merged PRs (30d)
- 36
Description
Hi everyone,
we would like to build the modules our multi-module maven projects on Jenkins concurrently.
Using `mvn -T` that works quite well, but unfortunately the logs are messed up as all the different hreads write to the console output.
mvnd offers a great way to visualize the progress of a parallel multi.-module build and - even mor eimportant - collects the log output and prints it after the build is finished. We would like to benefit from this feature in Jenkins as well.
So, I don't need the daemon itself in Jenkins, but this output optimiazion. If there is a way to port it to maven itself my problem would be solved too. For the time being I assume it's more realistic to use mvnd instead of mvn in Jenkins.
Maybe you have another idea how to solve my issue?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name any repository files, tests, or entry points. First clarify whether Jenkins log grouping should be implemented in mvnd or Maven itself, and define the expected console output and Jenkins integration behavior before locating the relevant build and logging code.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100