The primary artifacts are the yum / zypper / apt repositories of packages for various Linux distros, as detailed here: https://cwiki.apache.org/BIGTOP/how-to-install-hadoop-distribution-from-bigtop-050.html
On Mon, Jun 10, 2013 at 12:46 PM, Jay Vyas <[email protected]> wrote: > 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 ! > > > > >
