-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
-
1362.vee39a_d4b_02b_1
On CI systems using cloudy agents, it is typical for the local Maven repository to be empty at the start of a build, resulting in thousands of artifacts being downloaded. You can set up a proxy mirror to make this fast, but you still get tons of noise in the log. Jenkins devs have started to work around this using -Dorg.slf4j.simpleLogger.log.org.apache.maven.cli.transfer.Slf4jMavenTransferListener=warn to suppress messages about successful downloads, but even if you know about this workaround, it is not ideal: you then lack information in the log file which would be useful diagnostics if, for example, the build hanged in the middle of a socket connection.
Suggest having this plugin define a ConsoleAnnotatorFactory to hide these lines by default in a collapsing CSS box, so you can see that there were some downloads but do not need to look at all of them. Alternately, make withMaven define a ConsoleLogFilter that adds a ConsoleNote to each such line when it is emitted, akin to core MavenConsoleAnnotator.
- causes
-
JENKINS-72386 withMaven exits with unrecognized option --no-transfer-progress when using maven < 3.6.1
- Closed
- relates to
-
JENKINS-26462 Extract Maven builder to a separate plugin
- Open
- links to