Cos, regardless of this Power issue, wouldn't you think bigtop as a distribution should first consume artifact built by the distribution.
Anyway, how about this as a workaround. Could we add step "./gardlew install-hadoop" after Hadoop build and before the other components. for example: docker run -v `pwd`:/ws bigtop/slaves:trunk-fedora-22-ppc64le bash -l -c 'cd /ws ; ./gradlew hadoop-deb' *./gradlew install-hadoop* docker run -v `pwd`:/ws bigtop/slaves:trunk-fedora-22-ppc64le bash -l -c 'cd /ws ; ./gradlew spark-deb' docker run -v `pwd`:/ws bigtop/slaves:trunk-fedora-22-ppc64le bash -l -c 'cd /ws ; ./gradlew hbase-deb' ..... ..... ..... On Wed, Jan 27, 2016 at 10:27 PM, Konstantin Boudnik <[email protected]> wrote: > On Wed, Jan 27, 2016 at 10:05PM, MrAsanjar . wrote: > > Does the artifacts in maven "*local*" repository remain persistent > between > > bigtop component builds (i.e. Hadoop, Spark, HIve..)?? > > > > This question is relevant to any bigtop project (i.e. Spark, HBase, > > Hive,..) with build dependency on Hadoop libraries. > > > > In the event of Power8 (or any none-x86) build, these projects require > > Hadoop libraries for Power8 copied to the "*local*" maven repository > prior > > to the build. Maven public repository hosts only x86 version of Hadoop > > artifacts. > > > > For example, before building Spark for Power, bigtop Hadoop build for > Power > > must first get copied to the local maven repository. > > > > However, evidence suggests that either "install" option included in > > Hadoop's do-component-build file isn't working as designed :) or maven > > local repository is not persistent. > > > > mvn $ANT_OPTS $BUNDLE_SNAPPY -Pdist -Pnative -Psrc -Dtar ${MAVEN_OPTS} > > install "$@" > > if you're building this with Bigtop current CI, then it is possible that > ~/.m2 > isn't persisted between two different containers. However, if you're > running > component builds on the same machine, local repo-artifacts should be > persisted. > > Cos >
