[
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047876#comment-14047876
]
Roman Shaposhnik commented on BIGTOP-1286:
------------------------------------------
There's quite a bit of jenkins projects right now (some of them need to be
cleaned up, btw ;-)) but the reason for that is to make our builds
as asynchronous as possible. IOW, do you really want to rebuild all of Bigtop
packages when just the Pig packaging changes? I can't quite figure out how
would you achieve that level of independence if you condense everything into a
single top level job corresponding to bigtop-packages.
P.S. Perhaps, the easiest way to show what you really mean is to stan up a
dummy instance in the cloud and start prototyping?
> 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)
