Should also note to all listening that I did clear the workspace on our Jenkins build and rebuilt with the same error. This would have cleared our node-modules in place and deconflicted with existing. This could be one problem in testing changes that affect package versioning, but it isn’t likely THE problem at hand.
Thanks again, Rob +1 > On Jul 26, 2019, at 4:20 PM, Rob Foley <[email protected]> wrote: > > On my linux box I am able to successfully build/test the following: > > Repo: https://github.com/apache/incubator-flagon-useralejs > Branch: v2.0.1-RC1 > Node Version: v12.7.0 > NPM Version: 6.10.0 > > When I initially built master and switched to that branch, there was an > issue with the package-lock file having been changed, but that doesn't seem > like it'd be the issue. > > Rob > > On Fri, Jul 26, 2019 at 4:01 PM Joshua Poore <[email protected]> wrote: > >> Hi Folks, >> >> Builds are failing on Jenkins again and I could use help verifying whether >> I need to ask INFRA for help or whether there’s something wonky in our >> environment. >> >> >> Last night I pushed a RC branch for v2.0.1 and merged into master. The >> scope of the RC is a patch to fix broken npm dependencies and update >> dependencies to bubble up prototype pollution. >> >> I’ve pushed an update to the RC branch to include a changelog so that you >> all can see what I’ve done: >> https://github.com/apache/incubator-flagon-useralejs < >> https://github.com/apache/incubator-flagon-useralejs> >> >> Before pushing the branch (and master merge), I tested builds, ran unit >> tests, and integration testing with artifacts. I tested using nvm and >> tested against node 8.5, 10.10, 12.2, and 12.7 (latest). Everything but 8.5 >> passed (expected). >> >> See my testing on 12.7 here: >> https://issues.apache.org/jira/browse/FLAGON-429 < >> https://issues.apache.org/jira/browse/FLAGON-429> >> >> Builds failed after a merge with master. After they failed, I updated our >> Jenkins configs to test using node 12.7 (was 12.2). They passed. Then I >> regressed back to 12.2—they failed. Then I regressed back to last passing >> build (12.7) it then failed. I’m flummoxed. Looking into it a bit more. Our >> passing build was on a ubuntu bionic machine (build #75), and all our >> failing builds have been on ubuntu xenial machines. We’re using the x64 >> Linux version of node 12.7. >> >> The build error is always the same—it barfs on gulp-eslint v6.0.0. But >> that version runs on node 12.7.0 and the error is a error code 01 lifecycle >> error, which is always a npm version conflict. >> >> >> Going insane. Can someone please try and build the RC branch ( >> https://github.com/apache/incubator-flagon-useralejs < >> https://github.com/apache/incubator-flagon-useralejs>) on a Linux X64 >> machine and see if builds/tests run on npm 12.7 (I’ll take 12.2 too). This >> would be super helpful in debugging this issue. Should only take a minute >> or two to run install, built, and test. >> >> I’ll keep working on this tonight, but any help is MUCH appreciated. >> >> Josh
