[jira] [Commented] (BIGTOP-2474) Improve handling of gradle home

["Konstantin Boudnik (JIRA)" <ji...@apache.org>]

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

Konstantin Boudnik commented on BIGTOP-2474:
--------------------------------------------

It does make a lot of sense, really. I guess the current approach was a way to shift the startup time in the deployment and build of each package to, at least, once during the image creation. And it worked to some extent. But I like your approach more!

> Improve handling of gradle home
> -------------------------------
>
>                 Key: BIGTOP-2474
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2474
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 1.1.0
>            Reporter: Olaf Flebbe
>            Assignee: Olaf Flebbe
>             Fix For: 1.2.0
>
>         Attachments: BIGTOP-2474.patch
>
>
> The optimazation within {{build.gradle}} to create a {{/usr/share/gradle.home}} directory does not fully work. 
> At each time the file
> {{https://plugins.gradle.org/m2/gradle/plugin/org/nosphere/apache/creadur-rat-gradle/0.2.0/creadur-rat-gradle-0.2.0.jar}} 
> is downloaded.
> Propose to remove all this code alltogether and substitute it with a more docker-ish approach:
> Generate a clean container with the toolchain. Start it running ./gradlew within. Commit it as bigtop/slaves:trunk-os
> A local prototype looked very promising and decreased startup time. 



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