[
https://issues.apache.org/jira/browse/BIGTOP-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772312#comment-13772312
]
Konstantin Boudnik edited comment on BIGTOP-1081 at 9/19/13 9:06 PM:
---------------------------------------------------------------------
bq. Update: I've enabled Spark builds for the upcoming Bigtop 0.7.0 and it
seems that the problem isn't just limited to DEB side of things
this is a different issue: it seems that assembly files aren't found under
{{/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark/rpm/BUILD/spark-branch-0.8/assembly/target/spark-assembly-*-dist.tar.gz}}
It seems that the version of the artifact got changes and the mask "-*-"
doesn't work anymore. It needs to be "_*-" (new file name is {{
spark-assembly_2.9.3-0.8.0-incubating-SNAPSHOT-dist.tar.gz}})
bq. Do you need to pass the location of the auxiliary files?
for --source-dir I need {{bigtop-packages/src/common/spark}}. Now sure how to
refer to it.
There seems to be another issue. For RPM it runs:
{{sh
/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark//rpm//SOURCES/install_spark.sh
--build-dir=/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark/rpm/BUILD/spark-branch-0.8
--source-dir=/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark//rpm//SOURCES
--prefix=/var/tmp/spark-0.8.0.2-1-L31331
--doc-dir=/usr/share/doc/spark-0.8.0.2}}
But it looks that deb's build layout differs from that of rpm and the results
of mvn build are place under {{output/spark}} instead of {{build/spark}}. Am I
missing something?
was (Author: cos):
bq. Update: I've enabled Spark builds for the upcoming Bigtop 0.7.0 and it
seems that the problem isn't just limited to DEB side of things
this is a different issue: it seems that assembly files aren't found under
{{/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark/rpm/BUILD/spark-branch-0.8/assembly/target/spark-assembly-*-dist.tar.gz}}
bq. Do you need to pass the location of the auxiliary files?
for --source-dir I need {{bigtop-packages/src/common/spark}}. Now sure how to
refer to it.
There seems to be another issue. For RPM it runs:
{{sh
/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark//rpm//SOURCES/install_spark.sh
--build-dir=/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark/rpm/BUILD/spark-branch-0.8
--source-dir=/mnt/jenkins/workspace/Bigtop-trunk-Spark/label/centos5/build/spark//rpm//SOURCES
--prefix=/var/tmp/spark-0.8.0.2-1-L31331
--doc-dir=/usr/share/doc/spark-0.8.0.2}}
But it looks that deb's build layout differs from that of rpm and the results
of mvn build are place under {{output/spark}} instead of {{build/spark}}. Am I
missing something?
> spark build fails
> -----------------
>
> Key: BIGTOP-1081
> URL: https://issues.apache.org/jira/browse/BIGTOP-1081
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.7.0
> Reporter: Roman Shaposhnik
> Assignee: Konstantin Boudnik
> Fix For: 0.7.0
>
>
> Here's what I see when I try to build it on Ubuntu 12.03 LTS:
> {noformat}
> $ export SCALA_HOME=/opt/scala-2.10.2
> $ make spark-deb
> .....
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 15:19:45.772s
> [INFO] Finished at: Thu Sep 19 08:38:33 PDT 2013
> [INFO] Final Memory: 51M/1187M
> [INFO]
> ------------------------------------------------------------------------
> mkdir -p debian/tmp
> touch build-indep-stamp
> dh_testdir
> dh_testroot
> sh -x debian/install_spark.sh \
> --build-dir=`pwd` \
> --doc-dir=/usr/share/doc/spark \
> --prefix=debian/spark
> + set -e
> + getopt -n debian/install_spark.sh -o -l prefix: -l doc-dir: -l lib-dir: -l
> installed-lib-dir: -l bin-dir: -l source-dir: -l examples-dir: -l build-dir:
> -- --build-dir=/home/src/bigtop/output/spark/spark-0.8.0
> --doc-dir=/usr/share/doc/spark --prefix=debian/spark
> + OPTS= --build-dir '/home/src/bigtop/output/spark/spark-0.8.0' --doc-dir
> '/usr/share/doc/spark' --prefix 'debian/spark' --
> + [ 0 != 0 ]
> + eval set -- --build-dir '/home/src/bigtop/output/spark/spark-0.8.0'
> --doc-dir '/usr/share/doc/spark' --prefix 'debian/spark' --
> + set -- --build-dir /home/src/bigtop/output/spark/spark-0.8.0 --doc-dir
> /usr/share/doc/spark --prefix debian/spark --
> + true
> + BUILD_DIR=/home/src/bigtop/output/spark/spark-0.8.0
> + shift 2
> + true
> + DOC_DIR=/usr/share/doc/spark
> + shift 2
> + true
> + PREFIX=debian/spark
> + shift 2
> + true
> + shift
> + break
> + eval echo $PREFIX
> + echo debian/spark
> + [ -z debian/spark ]
> + eval echo $BUILD_DIR
> + echo /home/src/bigtop/output/spark/spark-0.8.0
> + [ -z /home/src/bigtop/output/spark/spark-0.8.0 ]
> + eval echo $SOURCE_DIR
> + echo
> + [ -z ]
> + echo Missing param: SOURCE_DIR
> Missing param: SOURCE_DIR
> + usage
> + echo
> usage: debian/install_spark.sh <options>
> Required not-so-options:
> --build-dir=DIR path to dist.dir
> --source-dir=DIR path to package shared files dir
> --prefix=PREFIX path to install into
> Optional options:
> --doc-dir=DIR path to install docs into
> [/usr/share/doc/spark]
> --lib-dir=DIR path to install Spark home [/usr/lib/spark]
> --installed-lib-dir=DIR path where lib-dir will end up on target
> system
> --bin-dir=DIR path to install bins [/usr/bin]
> --examples-dir=DIR path to install examples [doc-dir/examples]
> ... [ see source for more similar options ]
>
> usage: debian/install_spark.sh <options>
> Required not-so-options:
> --build-dir=DIR path to dist.dir
> --source-dir=DIR path to package shared files dir
> --prefix=PREFIX path to install into
> Optional options:
> --doc-dir=DIR path to install docs into
> [/usr/share/doc/spark]
> --lib-dir=DIR path to install Spark home [/usr/lib/spark]
> --installed-lib-dir=DIR path where lib-dir will end up on target
> system
> --bin-dir=DIR path to install bins [/usr/bin]
> --examples-dir=DIR path to install examples [doc-dir/examples]
> ... [ see source for more similar options ]
>
> + exit 1
> {noformat}
> So it seems that the build part goes fine, but the install one somehow fails.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
