CI/CD for Hexo

Table of Contents

1. Select your Git repository 2. Add a new delivery pipeline 3. Add actions 3.1 Build and test your Hexo website 3.1.2 Hexo version 3.2 Deploy website to server 3.3 Send notification to Slack 4. Summary

📚 Learn more about Hexo action features, integrations and alternatives.

With Buddy's delivery pipelines you can build, test and deploy Hexo websites on a single push to branch. The pipelines consist of actions that can be freely configured depending on your needs.

Hexo 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

Trigger modes

Manually (on click) — recommended for Production
On events (automatic) — recommended for Development
On schedule (on time interval) — recommended for Staging/Testing

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 3 actions that will perform the following tasks:

Build and test your Hexo website
Upload website to server
Send notification to Slack

3.1 Build and test your Hexo website

Build actions in Buddy are run in isolated containers run from official Docker images. When the pipeline is run, Buddy pulls the container, runs build commands, and uploads the results to the pipeline filesystem.

Look up and click Hexo on the action list to add it to the pipeline:

Hexo on action list

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

npm install
hexo generate$$

Hexo command console

3.1.2 Hexo version

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

Hexo action image

3.2 Deploy website to server

The website is ready for upload. Head to the Transfer section and select your deploy 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.3 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

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! 🔥

Bear in mind that this article is only a brief example of what Buddy can do. You can create additional pipelines for staging and production environments, integrate with your favorite services (AWS, Google, Azure), trigger tests on pull requests, build Docker images, and push them to the registry—the possibilities are unlimited.

If you want us to create a delivery pipeline for your project, drop a line to support@buddy.works – we'll be happy to help!

Last modified on September 22, 2023