CI/CD for Node.js

With Buddy, you can create a pipeline that builds, tests, and deploys Node applications on a push to Git. The configuration is super simple and takes 10 to 15 minutes.

Node pipeline example

Configuration is very easy and takes only a couple of minutes.

1. Select your Git repository

Buddy supports all popular Git hosting providers, including GitHub, Bitbucket, and GitLab. You can also use your own private Git server, or host code directly on Buddy.

Supported Git providers

2. Add a new delivery pipeline

Enter the pipeline's name, select the trigger mode, and define the branch from which Buddy will fetch your code:

Exemplary pipeline settings

Success

Event-based triggers allow you to run pipelines whenever a push is made to any branch in the repository, or whenever a branch, tag or a pull request is created or deleted. On event pipeline trigger mode

3. Add actions

Buddy lets you choose from dozens of predefined actions. In this example, we'll add 4 actions that perform the following tasks:

• Build and test Node.js app: download dependencies (npm, yarn, etc.), run tests, compile assets (npm tasks, webpack, etc.)
• Upload code to server together with compiled assets
• Restart application
• Send notification to Slack

3.1 Build your Node.js application

Look up and click Node.js on the action list to add it to the pipeline:

Action list

The Run tab lets you determine the commands to execute. The default commands are:

bashnpm install
npm test$$

Default build commands

3.1.2 Node version

You can change the version of Node and install missing packages & tools in the runtime environment tab:

Node action image

Tip

If your tests require a database to run, you can attach it in the Services tab: Services tab

3.2 Deploy application to server

The compiled application needs to be uploaded to the server. Head to the Transfer section and select your upload action (SFTP in our case):

File transfer actions

When adding the action, you can choose what and where should be uploaded:

SFTP action configuration

3.2.1 Node modules

Warning

Make sure to add node_modules to the ignore paths (Transfer tab) - we will install them on the server after the deployment in the next step. Ignore paths config

3.3 Install modules & restart application

Once the app is deployed, you can run additional commands on your server with the SSH action:

SSH action selection

In this case, we shall run npm install and restart the application with a script:

Restarting the application

3.4 (Optional) Send notification to Slack

You can configure Buddy to send your team a message after the deployment. In this example we'll use Slack:

Notification actions

Hint

If you add this action in the On Failure tab, Buddy will only send the message if something goes wrong with your build or deployment. On failure notification

4. Summary

Congratulations! You have just automated your entire delivery process 🍾🙌. Make a push to the selected branch and watch Buddy fetch, build, and deploy your project. With Continuous Delivery applied, you can now focus on what's really important: developing awesome apps! 🔥