Since an anonymous user cannot look into the configuration of a job The centos-6 job looks like:
---------------------
# setup configuration file
cat >
bigtop-deploy/vm/vagrant-puppet-docker/vagrantconfig_Bigtop-Docker-provisioner-centos-6.yaml
<<-__EOT__
docker:
memory_size: "4096"
image: "bigtop/deploy:centos-6"
boot2docker:
memory_size: "4096"
number_cpus: "2"
repo: "http://bigtop-repos.s3.amazonaws.com/releases/1.0.0/centos/6/x86_64";
distro: centos
components: [hadoop, yarn, spark]
namenode_ui_port: "54070"
yarn_ui_port: "8488"
hbase_ui_port: "64010"
enable_local_repo: false
smoke_test_components: [mapreduce, pig, spark]
jdk: "java-1.7.0-openjdk-devel.x86_64"
__EOT__
# destroy previous cluster
./gradlew docker-provisioner-destroy
# provision
./gradlew -Pconfig=vagrantconfig_Bigtop-Docker-provisioner-centos-6.yaml
-Pnum_instances=3 -Prun_smoke_tests=true docker-provisioner
# destroy provisinoed cluster
./gradlew docker-provisioner-destroy
---------------------
> Am 15.01.2016 um 22:37 schrieb Konstantin Boudnik <[email protected]>:
>
> Yup, we have it and we run it all the time (as in eating our own food with
> puppet deploy and docker provisioner). Check these here
> http://ci.bigtop.apache.org/job/Bigtop-Docker-provisioner-centos-6/
> http://ci.bigtop.apache.org/job/Bigtop-Docker-provisioner-debian-8/
>
> Cos
>
> On Fri, Jan 15, 2016 at 12:29PM, MrAsanjar . wrote:
>> Does bigtop build process includes any automated test? My understanding was
>> smoke-test execution was.
signature.asc
Description: Message signed with OpenPGP using GPGMail
