[
https://issues.apache.org/jira/browse/SENSSOFT-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556043#comment-15556043
]
Clay Gimenez commented on SENSSOFT-81:
--------------------------------------
[~lewismc] I've successfully put together a build for UserALE.js, but am
running into an environment issue that causes it to fail. The version of
Node.js available through "Execute shell script" is pretty out of date -- 0.10,
current LTS is 4.x and release is 6.x.
I'm not super familiar with Jenkins or how it sandboxes jobs -- is there a good
way for me to control the version of base binaries like Node for a particular
job? I don't want to accidentally clobber someone else's setup by installing a
new version of Node in a setup script, etc. I'm also looking into the
possibility of pulling a Node binary into the workspace and calling that
directly
Alternatively, but requiring help from Infra, it looks like there is a
[NodeJSPlugin|https://wiki.jenkins-ci.org/display/JENKINS/NodeJS+Plugin] for
Jenkins that might solve the issue. Regardless, we'll definitely need current
Node for UserALE and Tap builds.
> Setup Builds for All SensSoft components on builds.apache.org
> -------------------------------------------------------------
>
> Key: SENSSOFT-81
> URL: https://issues.apache.org/jira/browse/SENSSOFT-81
> Project: SensSoft
> Issue Type: Improvement
> Components: builds, Distill, STOUT, TAP, UserALE.js, UserALE.PyQt5,
> UserALEv3
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Blocker
>
> As part of moving towards incubating source releases we require the software
> source to build successfully and that if automated tests are available, that
> they pass.
> I will go ahead and create builds for all 6 SensSoft componenets right now
> over on builds.apache.org
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
