[
https://issues.apache.org/jira/browse/IMPALA-9107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17066837#comment-17066837
]
ASF subversion and git services commented on IMPALA-9107:
---------------------------------------------------------
Commit 850de91cc38b681e8cb5ea6194e4ba3415ea2c4d in impala's branch
refs/heads/master from David Knupp
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=850de91 ]
IMPALA-9107: Add timestamp to maven logging options.
We found that using awk to add a timestamp to the maven log can fail
if gawk is not installed. It seems better to configure maven to add
the timestamp itself.
Sample output:
========================================================================
Running mvn -U -Dorg.slf4j.simpleLogger.showDateTime=true
-Dorg.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss -B install -DskipTests
Directory /home/dknupp/Impala/ext-data-source
========================================================================
16:37:16 [INFO] Scanning for projects...
16:37:16 [INFO]
------------------------------------------------------------------------
16:37:16 [INFO] Reactor Build Order:
16:37:16 [INFO]
16:37:16 [INFO] Apache Impala External Data Source
[pom]
16:37:16 [INFO] Apache Impala External Data Source API
[jar]
16:37:16 [INFO] Apache Impala External Data Source Sample
[jar]
16:37:16 [INFO] Apache Impala External Data Source Test Library
[jar]
16:37:17 [INFO]
16:37:17 [INFO] ----------------< org.apache.impala:impala-data-source
>----------------
16:37:17 [INFO] Building Apache Impala External Data Source 1.0-SNAPSHOT
[1/4]
16:37:17 [INFO] --------------------------------[ pom
]---------------------------------
[etc...]
Change-Id: I10fbe9eb76b66e6ba00db9f95c91063410dd1b4e
Reviewed-on: http://gerrit.cloudera.org:8080/15537
Reviewed-by: Laszlo Gaal <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Reduce time spent downloading maven artifacts for precommit tests
> -----------------------------------------------------------------
>
> Key: IMPALA-9107
> URL: https://issues.apache.org/jira/browse/IMPALA-9107
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend, Infrastructure
> Affects Versions: Impala 3.4.0
> Reporter: Joe McDonnell
> Priority: Major
>
> When building Impala from scratch with an empty .m2 directory, maven needs to
> download a large number of jars and pom files. This is taking a long time and
> adds about 15-20 minutes to the build. For example, here is some output from
> a recent ubuntu-16.04-from-scratch, there is an 18 minute delay between the
> end of building the backend tests and the end of building the frontend:
> {code:java}
> 00:58:33 [100%] Built target hash-ring-util
> ...
> 01:16:37 [100%] Built target fe{code}
> Almost all of that time is spent downloading maven artifacts. Quite a few
> come from the maven central repository.
> This is taking way too much time, and we need to reduce it. The total size of
> artifacts being downloaded is not large. One approach would be to produce a
> tarball with the jars/poms that don't come from the CDP or CDH GBN repos. We
> can download that tarball and use it to either populate the .m2 directory or
> to stash it in IMPALA_TOOLCHAIN and use it as a maven repository with a
> file:// URI.
> This impacts all our jobs: ubuntu-16.04-from-scratch,
> ubuntu-16.04-dockerised-tests, all-build-options-ub1604,
> ubuntu-16.04-build-only, clang-tidy-ub1604
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
