You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Akhil PB (Jira)" <ji...@apache.org> on 2020/06/20 05:23:00 UTC

[jira] [Resolved] (YUNIKORN-160) release build on a fresh machine is failing

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

Akhil PB resolved YUNIKORN-160.
-------------------------------
    Resolution: Not A Problem

> release build on a fresh machine is failing
> -------------------------------------------
>
>                 Key: YUNIKORN-160
>                 URL: https://issues.apache.org/jira/browse/YUNIKORN-160
>             Project: Apache YuniKorn
>          Issue Type: Bug
>          Components: release
>            Reporter: Sunil G
>            Priority: Major
>
> While buildingĀ ./build-docker-images.sh on a fresh machine, command is failing
> {code:java}
> Successfully tagged yunikorn/yunikorn-scheduler-admission-controller:latest
> /Users/sgovindan/Work/releases/yunikorn/0.8.0/apache-yunikorn-0.8.0-incubating-src
> yarn install && yarn build:prod
> /bin/sh: yarn: command not found
> make: *** [build-prod] Error 127 {code}
> Proposal:
>  # Its not good to install "yarn" locally with the node version which we have in machine manages the web build process. In YARNUI2, i have seen this error regularly that some non-compatible package breaks the build
>  # Its better to do all the build process in docker which will have a sane version compatibility of all support s/w versions



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org