[
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13976174#comment-13976174
]
Roman Shaposhnik commented on BIGTOP-1286:
------------------------------------------
bq. the CI is living on Cloudera's donated AWS VMs. In order to change the
layout of the systems we need to have full access to the console. This step is
the MUST have: if project PMC can't control the donated infrastructure of the
project - we'll have to start looking for different options. Unfortunately.
Pinging Cloudera's folks to help us with this: guys, could you please help us
to clarify the situation with the resource on your side? Who's controlling
it/is in charge of the AWS? Please reach out to me privately - if needed - and
I will communicate with these people directly.
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).
Now, I think what would be a really useful discussion to have is how we should
be utilizing these resources and whether having the current approach of running
dedicated VMs for build is ideal or whether we should consolidate and use
containers to quickly spin up build environments. At any rate, I'd appreciate
if we could hash those out on ML, since JIRA could be a bit inconvenient for
those types of open-ended discussions.
> 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)
