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 2015/08/04 18:49:05 UTC

[jira] [Updated] (BIGTOP-1900) Upgrade bigtop/slaves images on bigtop's dockerhub

     [ https://issues.apache.org/jira/browse/BIGTOP-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Evans Ye updated BIGTOP-1900:
-----------------------------
    Component/s: build

> Upgrade bigtop/slaves images on bigtop's dockerhub
> --------------------------------------------------
>
>                 Key: BIGTOP-1900
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1900
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 0.8.0
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>             Fix For: 1.0.0, 1.1.0
>
>
> Same reason with BIGTOP-1898, we'll need to build new set of [bigtop/slaves|https://registry.hub.docker.com/u/bigtop/slaves/tags/manage/] images for those supported OSs. A simple way to do this is to setup a [CI job|http://bigtop01.cloudera.org:8080/view/Docker/job/Docker-Toolchain-Evans/] which spin up containers and runs bigtop_toolchain in side containers to have packages installed. Then we can manually commit and push images up to dockerhub.
> This is also blocking 1.0 release since the build process requires build/slaves images.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)