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 2017/05/03 17:56:04 UTC

[jira] [Commented] (BIGTOP-2753) Initial support for Debian-9

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

Evans Ye commented on BIGTOP-2753:
----------------------------------

{code}
22	COPY . /tmp/bigtop
23	RUN cd /tmp/bigtop && ./gradlew && cd && rm -rf /tmp/bigtop
{code}

Here we would like to boostrap gradle caches using ./gradlew.
I see a problem that if a user already have something built in the bigtop repo(output), then entire repo with gigs of artifacts will be 
copied and committed in the image.
AFAIK, there's no way to eliminate committed layer unless we manually squash the image.

Perhaps we can clone bigtop repo from github. That way it stays clean. Any better idea?

> Initial support for Debian-9
> ----------------------------
>
>                 Key: BIGTOP-2753
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2753
>             Project: Bigtop
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Olaf Flebbe
>            Assignee: Olaf Flebbe
>             Fix For: 1.3.0
>
>         Attachments: BIGTOP-2753.1.patch
>
>
> Support for building bigtop/puppet, bigtop/slaves for debian stretch (next stable).
> It features puppet-4.8, btw. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)