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
