[
https://issues.apache.org/jira/browse/BIGTOP-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254205#comment-14254205
]
jay vyas edited comment on BIGTOP-1576 at 12/19/14 11:20 PM:
-------------------------------------------------------------
[~rvs] [~cos] to add more context.
* How this sort of off-beat idea came about * :)
- When roman was travelling, we discussed how for the CI we could easily use
the {{bigtop-deploy/vm/docker-puppet}} recipes evans wrote, to test stuff.
- At that point, iirc, cos mentioned : We should add *vagrant* to bigtop
toolchain, so installation was taken for granted and we could leverage that
wherever we wanted to, however we wanted to.
*My 2 cents*
Although not *required per se* itd be great to run the {{vagrant-docker}}
recipes in the *CI* , after all
- thats the easiest way for users to spin up bigtop ,and so good to autotest it
works perfectly.
- and now that we can run vagrant to read rpms from {{output/}} ,
{{vagrant-docker}} can be used to *test the components that are built from
source*, for free , so saves us some duplicate work on the CI.
In any case --- this is mostly [~rvs]'s decision i think, as he's the ci
maintainer right now. so he knows best wether it will be something he would
like to use in jenkins.
was (Author: jayunit100):
[~rvs] [~cos] to add more context.
- When roman was travelling, we discussed how for the CI we could easily use
the {{bigtop-deploy/vm/docker-puppet}} recipes evans wrote, to test stuff.
- At that point, iirc, cos mentioned : We should add *vagrant* to bigtop
toolchain, so installation was taken for granted and we could leverage that
wherever we wanted to, however we wanted to.
although not *required per se* itd be great to run the {{vagrant-docker}}
recipes in the *CI* , after all
- thats the easiest way for users to spin up bigtop ,and so good to autotest it
works perfectly.
- and now that we can run vagrant to read rpms from {{output/}} ,
{{vagrant-docker}} can be used to *test the components that are built from
source*, for free , so saves us some duplicate work on the CI.
Iin any case --- this is mostly *romans* decision i think, as he's the ci
maintainer right now. so he knows best wether it will be something he would
like to use in jenkins
> Add Vagrant installation to bigtop_toolchain
> --------------------------------------------
>
> Key: BIGTOP-1576
> URL: https://issues.apache.org/jira/browse/BIGTOP-1576
> Project: Bigtop
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Priority: Minor
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1576.1.patch
>
>
> As [~cos]'s comment in BIGTOP-1564, this jira is going to "download the
> package and install it if the local vagrant version is lesser than expected".
> The patch will add a puppet recipe to automatically install Vagrant, helping
> to setup environment for running docker provisioner.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
