The current version of strider-docker-runner does not run npm install during the "prepare" step, so dependencies are never installed for node projects (see issue #18 on that project). strider-docker-runner uses this module (strider-runner-core) to do the actual command running, so I've forked and modified this to add a (very hacky) fix for that issue.
In this fork, npm install is called if another npm command (most likely npm test) is called and npm install has not yet been run. This means that npm install is called during the "test" phase rather than the "prepare" phase, which obviously isn't ideal from an organizational perspective, but it was the simplest fix that I found for the issue. In the future I may see if I can clean this up.
Just run those jobs. Decoupled from load balancing, job queues, etc.
var core = require('strider-runner-core');
core.process(data, provider, plugins, config, next);datais the mongoose job object. See the main strider repo for a schema.provideris an instantiated provider, such as strider-git.pluginsis a map of instantiated plugins (such as strider-node){id: plugin, ...}
Config parameters:
- env - a map for augmenting the ENV variables in all commands run
- io - an eventemitter for communication.
- dataDir - the directory to hold your code
- baseDir - base directory for this job
- cacheDir - cache directory
- cachier (see this file)
- logger
- log - log fn
- error - log errors
next is called with any errors as the first argument.