You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Evans Ye (JIRA)" <ji...@apache.org> on 2016/01/29 15:58:39 UTC
[jira] [Commented] (BIGTOP-2295) Docker tests should consume
current builds
[ https://issues.apache.org/jira/browse/BIGTOP-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15123545#comment-15123545 ]
Evans Ye commented on BIGTOP-2295:
----------------------------------
Hi [~oflebbe] this is an interesting topic.
Does user want to create a 1.1 SNAPSHOT cluster or user just want to use 1.1 Provisioner and Puppet features to create a cluster?
This patch propose the former, however it could potentially fail due to the bleeding edge of the master build. I don't know whether its good or not for users who'd like to try it out...
Another issue is that we need to apply a patch only to the release branch to change these defaults to stable, signed artifacts.
It'd be easier if we can just fix the url to something like this:
{code}
http://bigtop-repos.s3.amazonaws.com/releases/latest/debian/8/x86_64
{code}
And use another customized vagrantconfig.yaml in our CI builds.
> Docker tests should consume current builds
> ------------------------------------------
>
> Key: BIGTOP-2295
> URL: https://issues.apache.org/jira/browse/BIGTOP-2295
> Project: Bigtop
> Issue Type: Bug
> Reporter: Olaf Flebbe
> Assignee: Olaf Flebbe
> Fix For: 1.2.0
>
> Attachments: BIGTOP-2295.1.patch
>
>
> Die Download URL of packages point to 1.0 bigtop builds. They should point to a current stable build.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)