[jira] [Assigned] (BIGTOP-2213) tez build downloads amd64 nodejs executable

["Olaf Flebbe (JIRA)" <ji...@apache.org>]

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

Olaf Flebbe reassigned BIGTOP-2213:
-----------------------------------

    Assignee: Olaf Flebbe

> tez build downloads amd64 nodejs executable
> -------------------------------------------
>
>                 Key: BIGTOP-2213
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-2213
>             Project: Bigtop
>          Issue Type: Bug
>            Reporter: Olaf Flebbe
>            Assignee: Olaf Flebbe
>
> From the ppc64le build:
> {code}
> [INFO] Installing node version v0.10.18
> [INFO] Creating temporary directory /ws/output/tez/tez-0.6.2/tez-ui/src/main/webapp/node_tmp
> [INFO] Downloading Node.js from http://nodejs.org/dist/v0.10.18/node-v0.10.18-linux-x64.tar.gz to /ws/output/tez/tez-0.6.2/tez-ui/src/main/webapp/node_tmp/node.tar.gz
> {code}
> The {{frontend-maven-plugin}} checks installed version of nodejs, npm and bower and downloads them, if not suitable or found. Since this plugin only supports MacOSX, Linux and Windows (all on Intel Arch) this _will_ fail.
> Alternatively one could install nodejs in the slave image, but the versions in pom.xml do  not match. The  {{frontend-maven-plugin}} will detect this and will not download anything, if expected versions match. Unfortunately they will _not_ match, since the Version tez expects is rather old.
> Since tez is an architecture-independent package it is of questionable use, since a ubuntu/amd64 build of this package will be usable, too.
> Not sure how to proceed. Maybe we should not compile Arch-Independent software on all Archs ?



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