[
https://issues.apache.org/jira/browse/FLAGON-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16837976#comment-16837976
]
Joshua Poore commented on FLAGON-384:
-------------------------------------
uninstalled npm, reinstalled npm with
[nvm|[https://github.com/nvm-sh/nvm/blob/master/README.md]] to test builds with
multiple node versions.
Tested builds/test with node 4.6.0 (npm 2.15.9). replicated the build/test
fail. Also noted from console logs that there is a failure in npm install
process (Uncaught Exemption). [^useralejsNODE4_6_0_replication.rtf].
Tested builds/tests with node 8.2.1 (npm 5.3.0). builds and test passed. This
is an issue with the version of npm running on builds CI.
> useralejs Jenkins build is failing (#32-33)
> -------------------------------------------
>
> Key: FLAGON-384
> URL: https://issues.apache.org/jira/browse/FLAGON-384
> Project: Flagon
> Issue Type: Bug
> Components: UserALE.js
> Affects Versions: UserALE.js 1.0.0
> Reporter: Joshua Poore
> Assignee: Joshua Poore
> Priority: Trivial
> Fix For: UserALE.js 1.0.0
>
> Attachments: CIFail32useralejs, useralejsNODE4_6_0_replication.rtf
>
>
> [https://builds.apache.org/job/useralejs-ci/32/] [^CIFail32useralejs]
> Jenkins build failed after recent
> [commit|[https://github.com/apache/incubator-flagon-useralejs/commit/4bb5ebe8be228242861556c31ac6f4b78b929177]].
> This is weird because the commit exclusively incorporated changes to text
> referencing SensSoft, and links (Flagon–>SensSoft). This triggered a build
> test on Jenkins, which failed (see attachment).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
