CI/CD for Jekyll

Hint

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

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

Image loading... Jekyll pipeline example

1. Create a new project

Go to Projects and click Create new project. Select your Git hosting provider (Buddy, GitHub, Bitbucket, GitLab, or Private Server) and enter your project name.

Image loading... Create new project

2. Add a new pipeline

Navigate to Pipelines and click New pipeline. In the form, configure the following:

Name - Enter a descriptive name for your pipeline (e.g., "Deploy to production")
ID - Optional identifier for the pipeline
CPU - Select architecture: x64 or ARM64
Resources per pipeline run - Choose resource allocation (default: Workspace default)
Definition Location - Optionally check "Store configuration in a Git repository" to use YAML files

Click Add pipeline to create it.

Image loading... Add new pipeline

3. Configure workflow: contexts and triggers

After creating the pipeline, go to the Workflow tab to configure:

Image loading... Configure Workflow

Contexts - Click + to add Git branch/tag context or Environment. See Contexts.
Triggers - Click + to add Git events, Schedule, or Webhook. See Workflow Configuration.

4. 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 Jekyll website
Upload website to server
Send notification to Slack

4.1 Build and test your Jekyll website

Success

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 Jekyll on the action list to add it to the pipeline:

Image loading... Action list

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

bash
jekyll build
$

Image loading... Default build commands for Jekyll

3.1.2 Jekyll version

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

Image loading... Jekyll action image

Tip

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

4.2 Deploy website to server

The compiled application needs to be uploaded to the server. Head to the Deploy tab and select your upload action (Transfer in our case, where you can choose SFTP Target):

Image loading... File transfer actions

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

Image loading... SFTP action configuration

Hint

Targets allow to save pre-configured transfer server settings to be used across multiple actions.

4.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:

Image loading... 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. Image loading... On failure notification

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

Success

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.

Tip

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 Nov 20, 2025

Hugo Middleman