...
| Code Block |
|---|
|
./gradlew tasks |
Build components
The recommend build process is to use docker container from target OS-ARCH image to build specified components.
Here is example for build hbase for ubuntun-16.04/aarch64 platform ( {{BIGTOP_SRC_TOP}} is thetop of cloned bigtop source dir):
| Code Block |
|---|
|
$ cd BIGTOP_SRC_TOP
$ docker images # check if required bigtop/slaves:trunk-ubuntun-16.04-aarch64 is present
REPOSITORY TAG IMAGE ID CREATED SIZE
bigtop/slaves trunk-ubuntu-16.04-aarch64 eb812af63515 7 hours ago 3.039 GB
bigtop/puppet ubuntu-16.04-aarch64 82ef2c36b6e6 7 hours ago 311.5 MB
aarch64/ubuntu 16.04 a7d1ddc47ced 12 weeks ago 109.7 MB
$ docker run --rm -v `pwd`:/ws bigtop/slaves:trunk-ubuntu-16.04-aarch64 bash -l -c 'cd /ws ; ./gradlew hbase-deb' |
Then bigtop will fetch source code tarball from specified URL, applying patches, created patched source tarball/deb/srpm, build and package.
If everything goes well, target package can be found at BIGTOP_SRC_TOP/output/<package>
| Code Block |
|---|
|
$ ls output/hbase
hbase_1.1.9-1_all.deb hbase_1.1.9-1.debian.tar.xz hbase_1.1.9.orig.tar.gz hbase-regionserver_1.1.9-1_all.deb
hbase_1.1.9-1_arm64.build hbase_1.1.9-1.dsc hbase-doc_1.1.9-1_all.deb hbase-rest_1.1.9-1_all.deb
hbase_1.1.9-1_arm64.changes hbase_1.1.9-1_source.changes hbase-master_1.1.9-1_all.deb hbase-thrift_1.1.9-1_all.deb |