Mailing-List: contact user-help@bigtop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@bigtop.apache.org
Received-SPF: pass (nike.apache.org: domain of jayunit100@gmail.com designates
 209.85.215.46 as permitted sender)
MIME-Version: 1.0
Date: Mon, 10 Jun 2013 15:46:33 -0400
Message-ID: 
 <CAAu13zHkPkkoQNXc+O_jEdsWL+g2o2tS67+aA=XS=GCK_E0G8w@mail.gmail.com>
Subject: BigTop : Build Targets
From: Jay Vyas <jayunit100@gmail.com>
To: user@bigtop.apache.org
Content-Type: multipart/alternative; boundary=001a11c3ecdea7970404ded20968

--001a11c3ecdea7970404ded20968
Content-Type: text/plain; charset=ISO-8859-1

Hi again Big Top !

What are the "goals" as far as software artifacts coming out of bigtop ?  I
see that in the jenkins server there are all sorts of things, everything
from

- specific versions of tools which are considered part of the ecosystem
(i.e. the flume rpm)

http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Flume/label=fedora17/ws/build/hive/rpm/

- specific versions of non-ecosystem tools (like SOLR, which is completely
independent of Hadoop)

http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-All/

The definition on the web page is "Bigtop is a project for the development
of packaging and tests of the Apache Hadoop ecosystem."

Clearly, big top is doing alot of awesome stuff - building VMs with hadoop
distros in them for the whole ecosystem, testing the interoperability of
the software in those VMs, and compiling / building hadoop ecosystem tools
and packaging them up into a reusable and easily integrated structure.

However, its not clear what the "final" artifact that big top is producing
is.?

Maybe I don't understand the project definition correctly.  If so please
clarify :)

Thanks !

--001a11c3ecdea7970404ded20968
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div>Hi again Big Top ! <br><br>What are the &quot;go=
als&quot; as far as software artifacts coming out of bigtop ?=A0 I see that=
 in the jenkins server there are all sorts of things, everything from <br><=
br>
- specific versions of tools which are considered part of the ecosystem (i.=
e. the flume rpm)<br><br><a href=3D"http://bigtop01.cloudera.org:8080/job/B=
igtop-trunk-Flume/label=3Dfedora17/ws/build/hive/rpm/">http://bigtop01.clou=
dera.org:8080/job/Bigtop-trunk-Flume/label=3Dfedora17/ws/build/hive/rpm/</a=
><br>
<br></div>- specific versions of non-ecosystem tools (like SOLR, which is c=
ompletely independent of Hadoop) <br><br><a href=3D"http://bigtop01.clouder=
a.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-All/">http://bigtop01.clouder=
a.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-All/</a><br>
<br></div><div>The definition on the web page is &quot;Bigtop is a project =
for the development of packaging and tests of the Apache Hadoop ecosystem.&=
quot; <br><br></div><div>Clearly, big top is doing alot of awesome stuff - =
building VMs with hadoop distros in them for the whole ecosystem, testing t=
he interoperability of the software in those VMs, and compiling / building =
hadoop ecosystem tools and packaging them up into a reusable and easily int=
egrated structure. <br>
<br></div><div>However, its not clear what the &quot;final&quot; artifact t=
hat big top is producing is.? <br><br></div><div>Maybe I don&#39;t understa=
nd the project definition correctly.=A0 If so please clarify :)=A0 <br><br>
</div><div>Thanks !<br></div><div><br></div><div><br><br></div><div><br></d=
iv></div>

--001a11c3ecdea7970404ded20968--