You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Kevin W Monroe (JIRA)" <ji...@apache.org> on 2016/10/19 18:18:58 UTC

[jira] [Commented] (BIGTOP-2535) frontend-maven-plugin fails on ppc64le

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

Kevin W Monroe commented on BIGTOP-2535:
----------------------------------------

This isn't resolved yet (no one committed the patch to bigtop's git repo).  I had a look today and have a couple questions about the current (Sept 15) patch:

- I see you using wget instead of git clone.  Why?  Is git not available in the image?  It's fine if that's the case, but if you do have git available, you could save a couple wget / unzip steps.

- Every time you "RUN", you start at the root of an isolated filesystem, so this extra step isn't needed:
{{+RUN cd ..}}

- The license for the phantomjs blob that you're retrieving is BSD ([license from github|https://github.com/ibmsoe/phantomjs/blob/master/LICENSE.BSD]).  I'm no expert in licensing, so I'm not sure if there are any ramifications of including this for a bigtop docker slave's runtime environment.  Can anyone speak to potential conflicts or attribution requirement here?

> frontend-maven-plugin fails on ppc64le
> --------------------------------------
>
>                 Key: BIGTOP-2535
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2535
>             Project: Bigtop
>          Issue Type: Bug
>          Components: build, docker, ppc64le
>    Affects Versions: 1.1.0
>            Reporter: Amir Sanjar
>            Assignee: Amir Sanjar
>              Labels: build, docker, patch
>             Fix For: 1.2.0
>
>         Attachments: BIGTOP-2535.patch
>
>
> An alternate method  to install nodejs during maven build is to use frontend-maven-plugins. However, the current version of the plugins ( version =< 1.0.0) has hard coded path to x86 node binary.
> This issue has been resolved by pull request  https://github.com/eirslett/frontend-maven-plugin/pull/427, targeted for 1.2.0 release. 
> Meanwhile to unblock zeppelin, Tez, and Ambari 2.2.0 builds we need to include the plugin and PhantomJS as part of the docker slave image for PPC. 



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