You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "wuzhiguo (Jira)" <ji...@apache.org> on 2022/07/21 07:09:00 UTC

[jira] [Resolved] (BIGTOP-3745) Need a snapshot repository for rpm packages

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

wuzhiguo resolved BIGTOP-3745.
------------------------------
      Assignee: Kengo Seki
    Resolution: Done

> Need a snapshot repository for rpm packages
> -------------------------------------------
>
>                 Key: BIGTOP-3745
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-3745
>             Project: Bigtop
>          Issue Type: Wish
>            Reporter: wuzhiguo
>            Assignee: Kengo Seki
>            Priority: Major
>         Attachments: image-2022-07-17-18-33-13-210.png
>
>
> Hi Community,
> I met some problems when developing Bigtop Ambari Mpack.
> As we can see, there are some components still has problems in 3.1.0 and was fixed in
> 3.1.1(not released yet).
>  
> https://issues.apache.org/jira/browse/BIGTOP-3714
> https://issues.apache.org/jira/browse/BIGTOP-3735
> https://issues.apache.org/jira/browse/BIGTOP-3742
>  
> These problems blocked the development of Zeppelin/Tez for Mpack.
> And due to the network issues in China, we will fail to compile some components which will access Github in compile phase, like bower.
> As you can see the error message occurred in Hadoop compile phase in my machine below.
> !image-2022-07-17-18-33-13-210.png!
>  
> There are two choices we can successfully compile locally, which is
>  * Buy a VPN and open it while we're compiling the components.
>  * Buy a cloud machine which located in other countries.
> But only interested users will spend time or money do this, others may want to use the exists RPM directly.
> I know I will find a way to solve this problem, but those who only interested in Mpack development, they don't want to compile the components by themselves.
> That's why I suggest we can have a snapshot repository for unreleased version, every time we fixed the problems of components, we can trigger the Jenkins build job and upload the RPM packages to snapshot repository automatically.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)