30 April 2019

Buddy v2.2.26 Released (30-04-2019)


  • Added default value for variables in the ‘Pass Arguments’ action
  • Added info to the execution whether the pipeline was run with the API, Slack command or webhook (all three were marked as ‘manual’ before)

Bug fixes:

  • Fixed a bug with ENV VARs in the ApiKey field of the ‘Bugsnag’ action not getting resolved correctly.
  • The Deploy from scratch option didn’t work correctly when the ‘Wait for apply’ action preceded the deployment action – fixed
  • [Buddy Enterprise] Fixed a bug with the number of parallel actions not changing upon setting them via buddy configure
16 April 2019

Buddy v2.2.21 Released (16-04-2019)


  • Following up the recent design changes to deployments, we have updated the UI of all remaining actions
  • Actions configured with YAML can now be accessed in the GUI. You can also introduce changes and generate a new YAML for specific actions directly in the GUI
  • You can now see the sent message and its attachments in the logs of the Slack action
  • Improved error logging in Azure Kubernetes actions
  • Added support for new regions in the AWS actions (Stockholm, Beijing, Ningxia)

Bug fixes:

  • [Buddy Enterprise] Fixed a bug with builds using the previously built Docker image not working
  • Fixed a bug with cluster data not loading correctly upon changing the Kubernetes provider in the ‘Set image’ action
11 April 2019

Build container access for services

Services in build actions are a very popular feature allowing you to test applications that require, for example, a database or a Selenium driver to run.

Three weeks ago we added custom services that enabled tests of microservice applications—a very similar feature to docker compose. Until now, the communication was limited to one side: you could connect to a database or another service from the container that was triggering the tests, but it was impossible to connect the other way back.

We’re happy to announce that connections now work both ways.

9 April 2019

Buddy v2.2.17 Released (09-04-2019)

New features:

  • Build container access for services – from now on the main container of the build action is accessible for the microservices. You can set its hostname in the action’s ‘Services’ tab


  • New ‘Code’ view for intergrated projects
  • You can now import a synchronized repo from scratch in case of problems
  • It’s now possible to allow empty values in the ‘Find & replace’ action
  • Improved handling of errors in Kubernetes actions

Bug fixes:

  • When deploying from the filesystem the files from the .git folder were displayed incorrectly in the changeset which was slowing down the deployment in case of large repositories. Fixed
  • [Buddy Enterprise] Fixed a bug with adding the Sentry integration
  • [REST API] Fixes in adding the Cloudfront action
  • Minor fixes to the ‘Hugo’ action
3 April 2019

New feature: Run E2E Tests with

Cypress is a fast and easy to use test runner for front-end apps, featuring a number of options that help developers comprehensively test modern websites. The new integration allows you to automatically run tests on every change to code, recurrently on an interval, or on manual pipeline execution.

1 April 2019

Buddy v2.2.16 Released (01-04-2019)

New features:


  • Ignore paths now support ENV VARs
  • In case of connection problems when pulling an image from the Docker Hub, Buddy will try 3 times before marking the action as failed

Bug fixes:

  • If paths in the additonal cache were ending with a directory of the same name, they were cached incorrectly. Fixed
  • Fixed a bug with deleting variables with the Rest API
  • Fixed a bug with installing Helm in Kubernetes actions
28 March 2019

New feature: Version History for Pipelines

The core principle of Continuous Delivery is to version everything and everywhere: not only the source code, but also things like configuration files or SQL’s used for database migration. In 2017, we introduced YAML configuration for pipelines, enabling you to store pipeline configuration in the repo as buddy.yml. This way developers could easily track the changes to their workflow.

Today we add the option to browse pipeline history in projects configured with the GUI.