Buddy v2.1.44 Released (04-12-2018)

New features

  • Action-specific variables – you can now add variables that will be available only in builds and Run image action
  • Use custom Docker images without pushing them to the registry


  • New region in the New Relic action – you can now send notifications to Europe (before, only the US was available)
  • Pipeline and execution views are now loading faster. This solves the problem with executions that contained a lot of git fetch logs (thanks, Ilya!)
  • Improved Angular CLI configuration for Karma tests


  • On some occasions, changing the authentication mode in SSH and SFTP actions altered the connection details to the server. Fixed!

New feature: Deploy & Invoke Google Cloud Functions

With Google picking up the pace in serverless computing, Buddy doesn’t lag behind delivering two new actions that will let you deploy and invoke GCloud Functions.

In short, Functions act as application backends with no server provisioning or management, which is especially good for projects whose traffic patterns are hard to predict. They are event driven, which means they’re executed only when cloud events occur.

Buddy v2.1.43 Released (27-11-2018)

New features


  • In the CloudFront action, only the first 100 distributions were getting listed. From now on, you can choose from all distributions available
  • The text editor on the iOS has been improved for better display


  • Calling the API methods was taking a very long time (~4s). All times are now back to normal
  • Fixed a bug with running parallel actions if one of them was disabled

Parallel actions: Invitation to Beta

Fasten up your seatbelts and hold on to something as parallel actions are making their way to Buddy!

The feature many of you have been waiting for is soon to land on Buddy’s production servers. It will allow you to considerably save time on development and operations: for example, by running multiple deployments at once, or split tests in two and run them in parallel.

New feature: Trigger conditons for pipelines

The set of trigger conditions originally designed for individual actions is now available for entire pipelines. We have added this feature in response to users whose every pipeline action was triggered on the same condition (e.g. change to a repository path).

This way you no longer has to set it one by one in every action: just go to the pipelines settings and select the proper option.

Get started now

14 days of unlimited trial. No credit card required.