Fix SIGAR dependency connection timeout (#8258)

After enabling parallel builds for "mvn install", the sigar dependency
would sometimes resolve to the incorrect artifact repo for some of the
maven modules. This issue seems to be fixed by moving the definition of
the sigar dependency's artifact repo to the root POM.

Also, depending on network speeds, "mvn -q install" may take longer than
the default 10 minute timeout to print any output. Use travis_wait to
extend the timeout to 15 minutes.
This commit is contained in:
Chi Cao Minh 2019-08-08 18:13:18 -07:00 committed by Jonathan Wei
parent 76675d6163
commit b359c5b3d9
3 changed files with 9 additions and 9 deletions

View File

@ -42,8 +42,9 @@ env:
"
# Add various options to make 'mvn install' fast and skip javascript compile (-Ddruid.console.skip=true) since it is not
# needed. Use travis_retry to address intermittent connection timeouts when resolving the SIGAR dependency.
install: MAVEN_OPTS='-Xmx3000m' travis_retry $MVN clean install -q -ff ${MAVEN_SKIP} -DskipTests -T1.0C
# needed. Depending on network speeds, "mvn -q install" may take longer than the default 10 minute timeout to print any
# output. To compensate, use travis_wait to extend the timeout.
install: MAVEN_OPTS='-Xmx3000m' travis_wait 15 $MVN clean install -q -ff ${MAVEN_SKIP} -DskipTests -T1.0C
matrix:
include:

View File

@ -363,13 +363,6 @@
</resources>
</build>
<repositories>
<repository>
<id>sigar</id>
<url>https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/</url>
</repository>
</repositories>
<profiles>
<profile>
<id>strict</id>

View File

@ -182,6 +182,12 @@
<name>${repoOrgName}</name>
<url>${repoOrgUrl}</url>
</repository>
<!-- Only used by core, but moved to root for parallel build dependency resolution -->
<repository>
<id>sigar</id>
<url>https://repository.jboss.org/nexus/content/repositories/thirdparty-uploads/</url>
</repository>
</repositories>
<dependencyManagement>