CI/CD for Hugo

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

Buddy lets you create delivery pipelines that will build, test and deploy your Hugo website on a single push to branch. The pipelines consist of actions that you can configure depending on your needs. Hugo 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: Adding a new pipeline

Branch assignment — this is the branch from which Buddy will deploy. If you set the trigger mode to On push, Buddy will execute the pipeline upon every push to that branch.

Trigger modes

  • Manual (on click) — recommended for Production
  • On push (automatic) — recommended for Development
  • Recurrently (on time interval) — recommended for Staging/Testing

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 Hugo website
  • Upload website to server
  • Send notification to Slack

3.1 Build and test your Hugo website

Look up and click the Hugo action to configure it. Here you can choose the version of Hugo and determine the commands to execute. The default commands is:

hugo -c $WORKING_DIR

where $WORKING_DIR is an environment variable pointing to the directory with the pipeline's filesystem. Hugo default build command

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

Buddy's deployment is based on changesets. This means only changed files are deployed, which makes it lightning fast ⚡️.

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 to 'Actions run on failure', Buddy will only send a message if something went wrong with your build or deployment.

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!