8 March 2017

Buddy v1.4.39 Released

New features

  • Something BIG is coming. Stay tuned.


  • Better support of submodules in the Code tab
  • If you have two or more integrations of one type (eg. AWS) the list of integrated items in the action settings (eg. S3 buckets in Deployment to S3) will now display the ID’s of their parent integration
  • Every AWS action now displays the list of policies it requires. You can find the full list here

Bug fixes

  • Fixed bug with uploading files from the filesystem to a relative path on SFTP server
2 March 2017

Feature spotlight: Building Docker images

With Buddy you can build your own Docker images with source code from GitHub, Bitbucket and GitLab (or Buddy) repositories. In this release we’ve added context path support for Docker image builds—a good opportunity to present how to automate the delivery workflow for dockerized applications.

Docker app workflow

The workflow for the dockerized app is defined in a dockerfile kept in the repository along the source code and looks like this:

  1. Changes to application code
  2. Unit tests
  3. Build Docker image
  4. Push Docker image to registry
  5. SSH to the application server
    • Docker pull from registry
    • Stop current Docker container
    • Start new version

Buddy lets you save time and money by automating these steps so that you can focus purely on application coding.

Location of Docker image build action

Automating Docker build with Buddy

In this paragraph we’ll show you how to automate build and push to registry. As a result, on every change in the repository a new version of the application image will appear in the registry. You can fork this repository and use it as template, or use your own:

  1. Create a new project in Buddy and select the repository with the application
  2. Add a new pipeline, assign it to the Master branch, and set the trigger mode to On every push
  3. Add the Docker image action and select the dockerfile and context path that will be used for building the application.

    Note: Usually the dockerfile is located in the directory in which the image is built. However, sometimes the code structure requires the dockerfile to be moved somewhere else. In this case, you need to provide the context path.

  4. Select the registry to which the image will be delivered (Docker Hub, Amazon ECR, Private)

    You can use Environment Variables to define the tag with which the image will be pushed, for example $BUDDY_EXECUTION_ID or $BUDDY_EXECUTION_REVISION. This way every execution will create a new version of the image in the registry with an adequate tag.

  5. (Optional) Depending on the host you build your image on, you may want to use different variables to define the image values. These arguments are available upon clicking More options.

Once you add the action, every push to the repository will automatically build a new Docker image and push it to the registry with no need for action. You can also run the action manually:

Adding tests before Docker build

The principle rule of Continuous Deployment is that your code is always tested before it is deployed to the production server. This also applies to the code that you use to build your images. With Buddy you can automatically test every change pushed to the repository by adding a build action before building the Docker image:

  • Add Node.js at the beginning of the pipeline and define your tests. You can install any missing dependencies in the Packages & Setup tab

When ready, make a push or run the pipeline manually and watch Buddy execute your tests.

Re-running the Docker container after the build

The application is tested and the image is built. At this moment the image is usually run on a server. This too can be handled with Buddy:

  • Add the SSH action at the end of the pipeline, provide your server details and enter these commands:

      docker pull image:tag
      docker stop containername|| true
      docker run --name containername -d image:tag
SSH action details

You can use environment variables to store your credentials.

1 March 2017

Buddy GO: the Docker-based CI server with deployment tools

Buddy GO is a Docker-based CI server with Git hosting that you can install and use behind your own firewall. It sports the same features as the cloud instance of Buddy but is hosted and managed entirely on the premises. This is important for companies whose privacy policy requires to keep the code in-house, or for developers in remote areas with lagging internet connection.

28 February 2017

Buddy v1.4.38 Released

New features

  • New action: Build Docker image with context paths


  • Better support of errors for Rackspace deployments and Maven/Gradle builds
  • AWS Lambda now supports all AWS regions
  • Added commiter name and commiter email to Buddy parameters (useful eg. when sending notification of new version to Slack)
23 February 2017

Feature spotlight: PHP Unit

PHPUnit is a popular programmer-oriented testing framework for PHP. You can use it to test your code before the deployment so that you know the copy on your server is free of errors.

PHPUnit action details

Configuring tests and delivery with Buddy

There’s still a wide range of developers who haven’t heard or don’t know how to introduce Continuous Integration to their process. Buddy lets you set up the whole workflow in 10-15 minutes (either through GUI or YAML) and easily scale and expand once your projects grow bigger.

  1. Create a new project, choose your Git provider, and select your PHP repository.
  2. Add a new pipeline and switch the trigger mode to On every push
  3. Add PHPUnit action. You can install any missing modules in the Packages & Setup tab
  4. Add FTP/SFTP file transfer action and configure your deployment

You can also add the SSH action and use it, eg. to run composer install on your server.

This way every time you’ll make a push to the selected branch, Buddy will automatically test and deploy the changes to the server + run the desired SSH commands:

PHPUnit workflow

If your tests require a database to run, eg. MySQL, you can easily activate them in the Services tab:

Attaching database

A good practice is to add a conditional notification in the end that will send you a message in case the tests or the deployment have failed, for example to your Slack channel:

Slack conditional notification


If you’d like to learn more about using Buddy in PHP development, check out our guides on automating PHP dependencies and Wordpress themes with Buddy.

Happy coding!

22 February 2017

New action: Rackspace Cloud Files

Deploy files to Rackspace Cloud Files with the new file transfer action!

Rackspace Cloud Files is an online storage for large files and media: images, video, audio, as well as HTML, JavaScript and CSS files. The service ensures fast access to its content with a CDN utilizing over 200 servers around the world. Rackspace also provides developer tools for Java, Python, Node.js, Ruby, PHP, and .NET.

In order to deploy to Rackspace Cloud Files you need to provide your username and access token generated in your Rackspace account.

Rackspace Cloud Files
16 February 2017

Introducing: Expanded GitHub Integration

Since GitHub is the #1 Git provider among our users, we have decided to deepen the integration with the service by enabling the status of Buddy operations in the GitHub GUI.

The status will be visible in the following sections:

  • Code/Commits
  • Code/Branches
  • Pull requests
Pull request details

Use case: Pipeline as a build server

You can configure Buddy to automatically test your application on every push to any branch in your GitHub repository:

  1. Create a new project, choose GitHub as your provider, and select the repository that you want to use
  2. Create a new pipeline, set the trigger mode to On every push + set the Wildcard pattern to *
  3. Add a build action that will run the tests

This way every new commit pushed to the GitHub repository will be immediately tested with the results posted in GitHub.

Branch list on GitHub

Use case: Pipeline as a delivery tool

Another use case is configuring Buddy as a deployment tool for your Production server:

  1. Create a new project, choose GitHub as your provider, and select the repository that you want to use
  2. Create a new pipeline, set the trigger mode to Manual + assign the pipeline to your Master branch
  3. Add a file transfer action for your type of server (FTP/SFTP/cloud service, etc.)

Such pipeline will also send information to GitHub: you’ll be able to see which revision is currently deployed on the server on the commit history list. If for some reason the deployment hasn’t finished successfully, a proper label will be applied.

Commit history with labels
8 February 2017

Introducing: Configuration as Code (YAML)

Pipelines – the visual representation of a developer’s workflow – are one of the core features that make Buddy easy to use and configure. However, some of the developers prefer the classic way of managing configuration using YAML files.

This is especially true for users who:

  • have used another CI/CD software before and find it hard to switch to the GUI
  • need to store the history of configuration changes in the repository
  • want share their config files with other users
  • eat, code and sleep in their terminal :)

This is why we’ve decided to add support for YAML files as an alternative way of configuring pipelines. The option is available in the right column of the Pipelines tab.

IMPORTANT: Upon switching to the YAML mode any existing pipeline in the project will be removed. You can reproduce the pipelines by copying the configuration from YAML box and pushing it to the repository as buddy.yml. Please mind that the feature is still in beta and requires some polish, so any feedback is highly appreciated.

The complete documentation on how to use YAML in Buddy is available here.

Buddy YAML