[
https://issues.apache.org/jira/browse/BIGTOP-1576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14254205#comment-14254205
]
jay vyas commented on BIGTOP-1576:
----------------------------------
[~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.
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 also - those recipes as
the smoke test to validate bigtop rpms anyways, since they run the bigtop
smoke tests as well.
> 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)
