[
https://issues.apache.org/jira/browse/BIGTOP-1493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jay vyas updated BIGTOP-1493:
-----------------------------
Comment: was deleted
(was: I will try to learn some more about packaging and play some with this .
Meanwhile, for those interested - here are the some starter points around
packaging stuff for bigtop.
0) top level build.gradle file defines all bigtop tasks. it sources a
packages.gradle file that has the packaging tasks.
1) The bigtop.mk file defines all components in bigtop. it is referenced by
packages.gradle.
2) Each component has a do-component-build script. That script builds the java
project for you.
3) For deb and rpm specifics, those builders are in respective bigtop-packages/
directories. They
each use do-component-build to get the core jars. So the first step is to
write do-component-build for tachyon, i think.
4) For smoke tests, you can just dump a groovy script into
bigtop-tests/smoke-tests/tachyon.
For a simple example of how to package a single jar app, like mahout, you can
see the
blog post :
https://blogs.apache.org/bigtop/entry/getting_involved_with_bigtop_packaging .
)
> Add smoke test for tachyon
> --------------------------
>
> Key: BIGTOP-1493
> URL: https://issues.apache.org/jira/browse/BIGTOP-1493
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Reporter: jay vyas
>
> Tachyon as an in memory cache will be emerging as a common feature in hadoop
> and spark based clusters.
> Lets create a smoke test under the {{smoke-tests}} which uses the
> {{tachyon:///}} url.
> To get started with the smoke tests, you can
> 1) Run the vagrant recipe under bigtop-deploy/vm/vagrant-puppet . This will
> demonstrate the way you spin up a bigtop based hadoop cluster.
> 2) Now, you can do {{vagrant ssh}} into your cluster, and simply edit the
> smoke tests or install stuff. Re running the smoke-tests.sh file should test
> that your new tests work . At that point, just exit your VM, and commit your
> changes and submit the new patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
