The plug-in is being maintained by its owner/maintainers from a new home. The plug-in is still compatible with Hudson, however, the entry points for documentation and issue reporting have been combined in order to provide a single point of entry. Edit: The Jenkins plugin is no longer compatible, but there is a Hudson version.
Executes NodeJS script as a build step.
- Provides NodeJS auto-installer, allowing to create as many NodeJS installations "profiles" as you want
The auto-installer will automatically install a given version of NodeJS, on every Hudson slave where it will be needed.
- Allows to install globally some npm packages inside each installations, these npm packages will be made available to the PATH
- Allows to execute some NodeJS script, under a given NodeJS installation
- After installing the plugin, go to the global Hudson configuration panel (HUDSON_HOME/configure), and add new NodeJS installations.
For every Nodejs installation, you can choose to install some global npm packages.
Note that you might provide npm package's version (with syntax "email@example.com" for instance, or maybe better, "package@~0.1.0") in order to enforce reproductibility
of your npm execution environnment (note that the ~ syntax allows to benefits from bugfixes without taking the risk of a major version upgrade).
- Now, go to a job configuration screen, you will have 2 new items :
- On the "Build environnment" section, you will be able to pick one of the NodeJS installations to provide its bin/ folder
to the PATH.
This way, during shell build scripts, you will have some npm executables available to the command line (like bower or grunt)
See below :
- On the "Build" section, you will be able to add a "Execute NodeJS script" build step
This way, you will be able to fill a textarea with the script content you want to execute.
Note that you will have to select a NodeJS runtime you previously installed, to specify the NodeJS version you want to use
during your NodeJS script execution.
Known limitations / issues
- NodeJS Auto-installers will only work on linux x86/64 operating systems (support for Mac & Windows coming soon)
- NodeJS versions prior to 0.9.0 won't be available at the moment (directory structure was not the same as today on distribution site).
This might be handled in the future (this is exposed as PathResolver implementation) : don't hesitate to provide new
implementations for previous versions and submit a PR on github.
Error formatting macro: jiraissues: java.lang.RuntimeException: cannotconnect
0.2.1-h-1 (June, 23rd, 2014) Hudson version of 0.2.1.
0.2.1 (February, 10th, 2014)
- issue #21726 : Fix path separator issue when master & slave OS are not the same (kudos to ljohnston)
- Adding node executable at the beginning (instead of end) of the PATH (kudos to trecloux)
0.2 (August, 24th, 2013)
- Provided NodeJS Auto-installers based on available NodeJS versions on nodejs.org
Auto-installer will automatically install NodeJS for target node's OS/CPU type (only linux x86/64 supported ATM)
You will be able to define global npm packages installed during the NodeJS installation.
- Updated "Execute NodeJS script" build step, to allow selection of a NodeJS installation
- Added a new "Build environnment" checkbox allowing to provide a specific NodeJS installation to the PATH
This way, you will be able to execute npm packages, such as grunt or bower, in your shell scripts
0.1 (August, 13th, 2010)
- Provided new build step : "Execute NodeJS script"