[
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976220#comment-13976220
]
Konstantin Boudnik commented on BIGTOP-1286:
--------------------------------------------
bq. As a PMC we do have access to an AWS credentials assigned to the Bigtop
account that Cloudera is paying for (thanks for that by the way – this is
really appreciated!). We've got an ability to issue AWS API calls but we can't
login into the AWS management console (which I never felt was a problem anyway).
Good - that's all we need, as far as the control is concerned. Let's move this
discussion to the ML - JIRA isn't a best place for things. Once we agree on the
steps - we'll update or open new tickets.
> 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)
