Our asset build script now relies on node to be installed on $PATH on ci.mozilla.org. Can someone install node? The latest version should be fine. Example of our failing job: https://ci.mozilla.org/job/amo-assets/752/console
Assignee: server-ops → server-ops-devservices
Component: Server Operations: Web Operations → Server Operations: Developer Services
QA Contact: cshields → shyam
:fox2mike assigned to you since i wasn't sure how you wanted the node package installed. if it's puppetized, i would be happy to assist with the configuration.
(In reply to Chris Turra [:cturra] from comment #1) > :fox2mike assigned to you since i wasn't sure how you wanted the node > package installed. if it's puppetized, i would be happy to assist with the > configuration. It is puppetized, see puppet/trunk/modules/jenkins/master.pp Is node an rpm? Or it is some hackjob thing built from source? :)
CC'ing jabba too, he was working with some node stuff on ci.m.o as well.
we disabled our asset builds until this is fixed.
(In reply to Shyam Mani [:fox2mike] from comment #2) > It is puppetized, see puppet/trunk/modules/jenkins/master.pp > > Is node an rpm? Or it is some hackjob thing built from source? :) I see an rpm spec here for it https://github.com/vibol/node-rpm-spec (also, browserid.org uses it so it's probably already in use). I'd like to re-enable our CI jobs that depend on this so we're not flying blind.
is anyone able to check into this? can we do anything to help?
So jabba already did most of the work, I had to just add a symlink via puppet. [firstname.lastname@example.org ~]# which node /usr/bin/node Sorry for the delay here!
Assignee: server-ops-devservices → shyam
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
much appreciated all! I re-enabled our asset builds and they are passing
Status: RESOLVED → VERIFIED
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in before you can comment on or make changes to this bug.