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 2019/02/03 06:50:00 UTC

[jira] [Commented] (BIGTOP-3153) Switch to docker cp based solution to build inside containers

    [ https://issues.apache.org/jira/browse/BIGTOP-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759314#comment-16759314 ] 

Evans Ye commented on BIGTOP-3153:
----------------------------------

Simple test done on slave06 building bigtop-utils:
{code}
time ./gradlew bigtop-utils-pkg-ind --info
{code}

* docker cp
0m21.321s
0m13.499s
0m16.266s
* docker build
1m4.145s
0m54.675s
0m55.066s

> Switch to docker cp based solution to build inside containers
> -------------------------------------------------------------
>
>                 Key: BIGTOP-3153
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3153
>             Project: Bigtop
>          Issue Type: Sub-task
>          Components: build
>    Affects Versions: 1.3.0
>            Reporter: Evans Ye
>            Assignee: Evans Ye
>            Priority: Major
>
> There're several drawbacks using for current bigtop-ci/build.sh script:
> 1. Need to build and remove image for each build
> 2. If we do not remove the built image and try to rely on docker build cache, the requirements to reuse the cache is very high, hence most of the time the cache is discarded.
> 3. A newly built image need to re-download gradle/maven stuffs, which is redundant.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)