[jira] [Commented] (BIGTOP-1286) CI Cleanup

["jay vyas (JIRA)" <ji...@apache.org>]

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

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

[~rvs] This is a radical (maybe impossible) suggestion , but  could we gut the jenkins projects and replace them with a 4 top level jenkins projects?  I don't know if thats possible,  but it sure would be awesome to see a simple mapping of bigtop source code to the bigtop jenkins server.

 - bigtop-repos
   - centos
      |_pig
      |_hive
      ...
- bigtop-deploy
   vm
   |_ boxgrinder
        ....  
- bigtop-blueprints
   |_bigpetstore
   |_bps.jar
{noformat}

Then the build output would be way easier to make sense of.

> 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)