Details
-
Suggestion
-
Resolution: Fixed
Description
I'm sure maven builds are very common in Bitbucket Pipeline builds. As such, I think it would be worthwhile to separate the maven phases in the log output, as we always waste our entire "view in browser" portion of a build output log with just the downloading artifacts part of maven...
for example:
+ mvn clean install [INFO] Scanning for projects... Downloading: http://...nexus/content/groups/public/ca/nanometrics/maven/common-pom-java8/8.0.6/common-pom-java8-8.0.6.pom 614/614 B Downloaded: http://.../nexus/content/groups/public/ca/nanometrics/maven/common-pom-java8/8.0.6/common-pom-java8-8.0.6.pom (614 B at 0.8 KB/sec) Downloading: http://.../nexus/content/groups/public/ca/nanometrics/maven/common-pom/8.0.6/common-pom-8.0.6.pom 2/4 KB 3/4 KB 4/4 KB Downloaded: http://.../nexus/content/groups/public/ca/nanometrics/maven/common-pom/8.0.6/common-pom-8.0.6.pom (4 KB at 11.6 KB/sec) ...
At the very least, collapse this normal part of maven that creates a lot of logs, and even better, separate each phase of the Maven build with its own section in the log "tree" that gets built. Presumably, this would mean we could expand each section and not have to download the raw log each time we want to take a quick look.