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

["Evans Ye (JIRA)" <ji...@apache.org>]

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

Evans Ye resolved BIGTOP-1900.
------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.1.0)

This is fixed. I've pushed all the 1.0 supported OS images on [bigtop dockerhub|https://registry.hub.docker.com/u/bigtop/slaves/tags/manage/].
The images are built by the [CI job|http://bigtop01.cloudera.org:8080/view/Docker/job/Docker-Toolchain-1.0.0/]  and pushed to dockerhub manually.
We might need to have better naming in the future, but so far it works fine for all the CI use cases.



> 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
>
>
> 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)