infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua Poore (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-18526) Apache Flagon Builds Failing -- Failed node.js/npm install
Date Thu, 30 May 2019 04:59:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-18526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16851520#comment-16851520
] 

Joshua Poore commented on INFRA-18526:
--------------------------------------

Success. That did it. Builds are passing. Resolved with my thanks!

> Apache Flagon Builds Failing -- Failed node.js/npm install
> ----------------------------------------------------------
>
>                 Key: INFRA-18526
>                 URL: https://issues.apache.org/jira/browse/INFRA-18526
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>         Environment: node.js, linux
>            Reporter: Joshua Poore
>            Priority: Major
>
> Builds for our userale.js sub-project began failing [1] after minor updates to Readmes,
Doap, and other documentation following a recent project name change [2]. 
> We re-ran tests locally to replicate build error. We found that error [3] is typically
linked to node.js version conflicts with packages. We were able to replicate this error testing
on the node.js version in Jenkins configs (v4.6.0). Builds were successful on modern versions
(v8.2.1<>v11.10.0). 
> We attempted to update node.js environment in Jenkins configs [4] (8.2.1 & 11.10.0).
Re-running Jenkins build, resulted in new errors indicating failures to install new versions
of node.js [5] . We have confirmed that file paths to modern node.js versions are accurate.
> see related project ticket: https://issues.apache.org/jira/browse/FLAGON-384
> REFS:
> [1] https://builds.apache.org/job/useralejs-ci/32/
> [2] https://github.com/apache/incubator-flagon-useralejs/commit/4bb5ebe8be228242861556c31ac6f4b78b929177
> [3] Console Logs (error)
> npm ERR! Linux 4.15.0-1029-gcp
> npm ERR! argv "/home/jenkins/jenkins-slave/workspace/useralejs-ci/node-v4.6.0-linux-x64/bin/node"
"/home/jenkins/jenkins-slave/workspace/useralejs-ci/node-v4.6.0-linux-x64/bin/npm" "run" "build"
> npm ERR! node v4.6.0
> npm ERR! npm  v2.15.9
> npm ERR! code ELIFECYCLE
> npm ERR! useralejs@1.1.0 build: `gulp build`
> npm ERR! Exit status 1
> npm ERR! 
> npm ERR! Failed at the useralejs@1.1.0 build script 'gulp build'.
> npm ERR! This is most likely a problem with the useralejs package,
> npm ERR! not with npm itself.
> npm ERR! Tell the author that this fails on your system:
> npm ERR!     gulp build
> npm ERR! You can get information on how to open an issue for this project with:
> npm ERR!     npm bugs useralejs
> npm ERR! Or if that isn't available, you can get their info via:
> npm ERR! 
> npm ERR!     npm owner ls useralejs
> npm ERR! There is likely additional logging output above.
> npm ERR! Please include the following file with any support request:
> npm ERR!     /home/jenkins/jenkins-slave/workspace/useralejs-ci/npm-debug.log
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: dev@senssoft.incubator.apache.org poorejc@apache.org
> Finished: FAILURE
> [4] https://builds.apache.org/job/useralejs-ci/configure
> [5] Console log from https://builds.apache.org/job/useralejs-ci/43/console 
> [useralejs-ci] $ /bin/sh /tmp/jenkins8401824710934389459.sh
> /usr/bin/env: 'node': No such file or directory
> /usr/bin/env: 'node': No such file or directory
> /usr/bin/env: 'node': No such file or directory
> Build step 'Execute shell' marked build as failure
> Sending e-mails to: dev@senssoft.incubator.apache.org poorejc@apache.org
> Finished: FAILURE



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message