Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Otto Fowler
Also, since I changed the profiles to not run the rpm docker if you are in docker already ( and put the rpm tools into the ansible docker ) a while ago we may be able to build world in the ansible image, and point folks having issues to that…. On November 27, 2017 at 10:57:03, Otto Fowler

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Otto Fowler
OK, So I have >mvn clean package working in docker. I want to try a couple of things and maybe I can throw a pr together. On November 27, 2017 at 10:03:31, Otto Fowler (ottobackwa...@gmail.com) wrote: First issue is that we need c++ 11 on centos 6.8 On November 27, 2017 at 09:53:55, Simon

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread zeo...@gmail.com
Note that I cleaned up the ansible scripts that install C++ 11 in my latest PR , but it's not super relevant to this conversation. Jon On Mon, Nov 27, 2017 at 10:42 AM zeo...@gmail.com wrote: > That was also required for bro

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread zeo...@gmail.com
That was also required for bro 2.5.2, so I did that here . Feel free to reuse the approach elsewhere Jon On Mon, Nov 27, 2017 at 10:03 AM Otto Fowler wrote: > First issue is that we need

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Otto Fowler
First issue is that we need c++ 11 on centos 6.8 On November 27, 2017 at 09:53:55, Simon Elliston Ball ( si...@simonellistonball.com) wrote: Well, that’s good news on that issue. Reproducing the problem is half way to solving it, right? I would still say there are some systemic things going

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Simon Elliston Ball
Well, that’s good news on that issue. Reproducing the problem is half way to solving it, right? I would still say there are some systemic things going on that have manifested in a variety of ways on both the users and dev list, so it’s worth us having a good look at a more robust approach to

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Otto Fowler
I can reproduce the failure in out ansible docker build container, which is also centos. The issue is building our node on centos in all these cases. On November 27, 2017 at 07:02:51, Simon Elliston Ball ( si...@simonellistonball.com) wrote: Thinking about this, doesn’t our build plugin

Re: [DISCUSS] NPM / Node Problems

2017-11-27 Thread Simon Elliston Ball
Thinking about this, doesn’t our build plugin explicitly install it’s own node? So actually all the node version things may be a red herring, since this is under our control through the pom. Not sure if we actually exercising this control. It seems that some of the errors people report are more

Re: [DISCUSS] NPM / Node Problems

2017-11-26 Thread RaghuMitra Kandikonda
Looking at some of the build failure emails and past experience i would suggest having a node & npm version check in our build scripts and moving dependency management to yarn. We need not restrict the build to a specific version of node & npm but we can surely suggest a min version required to

Re: [DISCUSS] NPM / Node Problems

2017-11-24 Thread Nick Allen
Yes, it is a problem. I think you've identified a couple important things that we could address in parallel. I see these as challenges we need to solve for the dev community. (1) NPM is causing us some major headaches. Which version do we require? How do I install that version (on Mac,