[jira] [Commented] (BIGTOP-1917) Simplify gradle creating apt/yum repositories for better CI

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

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

Konstantin Boudnik commented on BIGTOP-1917:
--------------------------------------------

A couple of comments:
- any reason to move {{apt}} and {{yum}} tasks code all the way to the bottom of the file from where they were? Makes them kinda separated from the rest of their dependencies... But it might be my personal preference ;)
- It seems that new tasks do not place a success flag file eg {code}touchTargetFile(BOM_map["${variable}_TARGET_YUM"]){code}
- in the new version there's no way anymore to build apt/yum repo just for a few components explicitly. Is it intentional?

> Simplify gradle creating apt/yum repositories for better CI 
> ------------------------------------------------------------
>
>                 Key: BIGTOP-1917
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-1917
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Olaf Flebbe
>            Assignee: Olaf Flebbe
>         Attachments: BIGTOP-1917.1.patch
>
>
> I propose to simplify the {{packages.gradle}} in order to better support the new docker based CI .
> So all the target-yum / target-apt tagets have been removed and a simple repository creation is done by gradle yum/apt which can be run after all packages have been done. Complexity of gradle is removed as a side effect.
> In the CI the only thing to be done is to schedule a "gradle yum/apt" .
> Maybe we have to discuss to remove the dependencies at all in order to generate *anything* if something failed before.



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