[
https://issues.apache.org/jira/browse/BIGTOP-1286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975895#comment-13975895
]
Konstantin Boudnik commented on BIGTOP-1286:
--------------------------------------------
Great idea, Jay! A few comments:
# 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.
Contingent on the above:
# github.com/apache/bigtop is a mirror of ASF git repo. Could you please
elaborate what's the role of the hook?
# smoke test jobs should be there. They might not be obviously named, as [~rvs]
has an interesting opinion about naming things ;)
# linux packages _can not_ be published to Maven. Sorry
# does bigpetstore produces any java libraries that are used by projects that
are downstream of Bigtop?
# if vagrant helps to speed up cluster spin-up - it'd be great!
# boxgrinder doesn't seem to be supported well. And looks like it doesn't
support Ubuntu. I guess we'd better look for other options. I am not an expert
on these sort of things, though.
BTW, I think order of building packages and running smoke tests steps has to be
swapped ;)
> 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)
