[
https://issues.apache.org/jira/browse/AMBARI-14057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15034454#comment-15034454
]
jun aoki commented on AMBARI-14057:
-----------------------------------
[~jaimin] thank you for picking up and I'm all for it.
We don't have a good control on Apache's build environment(builds.a.o) and has
some version of nodejs.
We should avoid the situation like this. The best I think is to Dockerlize our
build/test environment and make it our official build environment so that
1. Contributors don't need to depend on a document (which could be outdated any
given time) to set up their environment.
2. And third party environment, like builds.a.o, might have an incompatible
environment but can work with it as long as it has Docker. (and builds.a.o do
support Docker)
To go with that approach, we should fix our Dockerfile (which is currently
outdated)
https://github.com/Pivotal-Hadoop/ambari/blob/trunk/dev-support/docker/docker/Dockerfile
And a script to run Docker container, something like
https://github.com/apache/incubator-geode/blob/develop/dev-tools/docker/compile/start-compile-docker.sh
Then we set Jenkins slave run the shell script to start a bash session in a
container, and run mvn command.
> ambari-web build is failing on trunk
> ------------------------------------
>
> Key: AMBARI-14057
> URL: https://issues.apache.org/jira/browse/AMBARI-14057
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.2.0
> Reporter: Jaimin D Jetly
> Assignee: Jaimin D Jetly
> Priority: Critical
> Fix For: 2.2.0
>
>
> Last several runs have failed with build failure in ambari-web.
> E.g. https://builds.apache.org/job/Ambari-trunk-Commit/3905/consoleFull
> {code}
> [INFO] --- exec-maven-plugin:1.2.1:exec (compile-brunch) @ ambari-web ---
> Error: Brunch 2+ requires node v4.0+. Upgrade node or use older brunch for
> old node.js: npm i -g brunch@1
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
