[ 
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976186#comment-13976186
 ] 

jay vyas commented on BIGTOP-1286:
----------------------------------

1) forget git repo hooks , we can poll . 
2) sure, the smokes may be there.  we can copy the job over to a new server if 
we create one. but remember we're about to redo alot of the smokes very 
shortly, starting small with BIGTOP-1221 and maybe even more.
3) did i say maven ? sorry, i meant s3 :)
4) yes, just a jar file.  Right now its published here : 
bigpetstore.s3.amazonaws.com/maven/BigPetStorePro .  We can move it to the 
org.apache.bigtop repo just like itest . 
5) the vagrant cluster tests will validate both the repo, the vagrant recipes, 
the puppet recipes, the smoke tests, AND the individual components, all in one 
shot.  They will speed up release / dev /test cycle in that sense. 
6) packer is the way things are headed. but im no expert on vm builders either. 
 i think [~mackrorysd] or [~evans ye] might be able to help in that dept if  
any spare cycles.  till then, i think replacing the ISOs with vagrant boxes is 
a pretty good step forward.  ? 

> CI Cleanup
> ----------
>
>                 Key: BIGTOP-1286
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1286
>             Project: Bigtop
>          Issue Type: Improvement
>          Components: Build, Tests
>    Affects Versions: backlog
>            Reporter: jay vyas
>             Fix For: backlog
>
>
> Time to clean up the CI ! 
> - 24 inactive projects
> - 30+ broken projects 
> - Several sandbox projects "test-cluster" "SmokeClusterOld" 
> **PROPOSAL:** we consider creating a new jenkins build master server 
> altogether, which is minimal, and keep http://bigtop01.cloudera.org:8080/ 
> around in the interim?
> 1) Add a build hook to github.com/apache/bigtop 
> 2) Create the following jobs: 
> - Runs the smoke tests against a working yarn+hdfs cluster
> - Builds rpms and debs and publishes to maven (on a slave) 
> - Builds bigpetstore :) and publishes to maven (on a slave)
> - Spins up a vagrant bigtop instance and runs a simple smoke test on it 
> (calculate pi), again on a slave. 
> - Packages BoxGrinder appliances (not sure if we are still maintaining these, 
> or moving to packer.  )?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to