[
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14131794#comment-14131794
]
jay vyas commented on BIGTOP-1286:
----------------------------------
I think this is what an immutable CI for bigtop would look like, right? I
could be oversimplifying, let me know.
- build docker images for each distro
- commit code to bigtop-1286 which pulls and builds bigtop on each distro
- provision a single m1 xlarge
- run the docker provisioners nightly on ^
> Build an immutable BigTop CI.
> -----------------------------
>
> 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
>
>
> UPDATE : The BigTop CI went down. Lets build a new one. And lets make it
> immutable.
> OLD CONTENTS : 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.3.4#6332)
