Skip to content
Node.js container support for cloudbees
Find file

Node.js support on CloudBees.

ClickStacks and CloudBees

This should work with standard node.js apps packaged up of the zip of the application directory (the dir with the package.json in it) - please do ask any questions on!forum/cloudbees-dev as we flesh it out.

If you want the quickest way to get going with node.js on cloudbees - fire up the clickstart:

Stacks are specified when you deploy an app.

You can specify the stack to use either by name, or and -RPLUGIN.SRC.= - this is called a "remote" plugin and is useful for getting the latest version of things.

For example, to run this stack:

Clone this repo and run:

bees app:deploy -t nodejs -R PLUGIN.SRC.nodejs= 

(the is just a, um, sample app! Unzip to see the structure). - is the url to the currently published version of this clickstack. We also maintain an alias that points to the latest version, use -t nodejs when deploying (means that with any redeploys, your app will use the latest production version of nodejs that we have).

This stack uses npm to install any required packages, and expects applications to be packaged up as a zip. Obvious the best way to do npm install is in a Jenkins job - which is what the ClickStart sets up for you.

Usage Example

bees app:deploy -t nodejs 

That is it. You can see this running at

Selecting a NodeJS Version

You can select the NodeJS version to be using by passing runtime parameter node.version

-R node.version=0.11.7 


It looks for a main.js by default. You can set a config variable of "main_js" to override this. If you have dependencies in your package.json - run npm install before you zip up your application for deployment.

Updating this stack

  • fork this repo (maybe)
  • update ... what you need to update
  • make publish

This will make a zip of the stack, and push it to a repository via your cloudbees credentials. You then use the resulting URL in the STACKURL above.

Something went wrong with that request. Please try again.