New integration: Honeybadger

Honeybadger helps developers identify and debug errors & exceptions when they occur in the production so you can quickly decide whether to apply a hotfix or roll back changes.

You can also use Honeybadger for:

  • Uptime monitoring – checking your sites & services externally from different locations in the world and notifying you if they’re down
  • Check-in monitoring – your services & cron jobs check in to Honeybadger and it notifies you if they go missing

New integration: Vultr

Following your request, yet another IaaS joins the already extensive stack of Buddy: Vultr.

Since 2014 the Australian service has been steadily gaining recognition as a reliable, high performance cloud. Spanning 15 datacentres across the globe, Vultr provides developers with one-click apps allowing you to launch WordPress blogs, development environments and game servers with a single click – just like running deployments from Buddy.

New integration: DigitalOcean Spaces

In response to the recent launch of DigitalOcean Spaces, we have added a dedicated deployment action to the service.

Spaces are DO’s response to the Amazon S3 buckets, a convenient and budget-wise means to store and serve large amounts of data—such as videos, media and static HTML sites with CSS and JS files that can be linked to your side, etc.

New feature: Trigger condition in actions

Following the update to builds, trigger conditions are now available in all actions. This means you can skip actions if they don’t fulfil certain requirements.

The following conditions have been added to the action settings:

  • Always execute - the action will run every time the pipeline is executed
  • Execute on change in repository - the action will be run only if Buddy detects a commit has been pushed to the pipeline’s branch. This is useful, for example, if you want to re-deploy the application in the same revision to the server and don’t need to compile it again
  • Execute on change in repository paths - the action will be executed only on a change to specific folder in the repository

Buddy v1.5.55 Released

New features

  • Trigger conditions in actions
  • New integration: DigitalOcean Spaces
  • New integration: Vultr
  • New integration: Honeybadger


  • The filesystem type in the Docker Build action has been changed from AUFS to overlay2. This has solved the problems reported by some of our clients and speeded up the action up to 3 times
  • You can now precisely schedule build execution in recurrent pipelines settings
  • Buddy parameters are now supported in the working directory of the SSH action and the target branch field of the Git push action
  • Removing pipelines with monitoring actions could be very time-consuming due to the time needed for executions removal. We have fixed the indexing and reduced it to a couple of milliseconds at most
  • The timeout for GitLab connections has been prolonged to 5 minutes (the response time from GitLab can be very long which sometimes made the integration to crash)
  • It is now possible to look up pipelines on the Table view


  • Fixed namespace support in methods checking the job status in the Run Job (K8s & GKE)
  • Projects to which you don’t have permissions in the Deploy to Google App Engine action will no longer be listed

Buddy v1.5.54 Released

New features

  • New integration: Rollbar
  • New integration: Datadog
  • You can now use SSH keys defined in the environment variables in actions using SSH authorization (SFTP, SSH, Rsync, Git push, etc.)
  • New version of Sandboxes released for private beta testers


  • Rsync deployments now support Buddy keys
  • Cloning a pipeline will now clone static files and visibility settings, too
  • It is now possible to set up the mount path for the pipeline filesystem in build actions with YAML/API


  • Fixed browsing in the Rsync action (didn’t work as Rsync was authorized with an SSH key)
  • Fixed bug with testing and sending Slack attachments

New feature: Sentry integration

We’re happy to announce that Buddy officially supports Sentry bug tracking and reports!

With the release of Buddy v2.0.2, the integration is available for both cloud and on-premises installations of Sentry.

Sentry helps developers identify and debug errors before they make it to production. With a detailed insight into the error you can quickly decide whether to apply a hotfix or roll back changes. The tool lets you apply filters to stack traces to reduce noise and reproduce errors without user feedback with each bug’s history of events and users actions—a perfect complement to Buddy’s delivery pipelines.

Feature update: Deploy builds to Heroku

In response to numerous requests from the community, we’re happy to announce that our Heroku action now supports build deployments.

Until now, it was only possible to deploy raw files from the repository. With the last release you can use Buddy to build your application first and deploy it to Heroku in its final form with artifacts and dependencies. This solution brings a series of benefits:

AWS CodeDeploy – Deployment status update

AWS CodeDeploy enables developers to automate code deployments to Amazon EC2 instances and on-premises servers.

It scales with the cloud infrastructure, allowing to deploy the same application revision to multiple nodes at once across different environments + tracks application health according to configurable rules.

Buddy v1.5.53 Released

New features

  • Buddy key regeneration
  • AWS CodeDeploy: added ‘Wait until deployment has finished’ option
  • Heroku: you can now deploy files processed in build actions, for example you can build assets with Gulp or Grunt, and push the source code to Heroku


  • Better error support in AWS CodeDeploy & Elastic Beanstalk when authentication data does not allow to add an S3 bucket (deployment to EB requires permissions to S3 buckets). Click here for the full list of AWS policies
  • Fixed error support when too little RAM is assigned to build actions. At the moment, all build actions are executed in Docker containers with 2GB of RAM. In a couple of weeks you will be able to buy custom plans with more RAM and vCPU’s
  • It is now possible to define trigger conditions with API and YAML
  • We’ve changed the way changes are fetched to the pipeline’s filesystem, which solved lots of problems with .git metadata
  • Short hash has been added to the execution view (until now you had to open an extra link to copy the revision of the execution)


  • Fixed bug with synchronizing private repositories in case authorization data used for checkout contained a question mark ?
  • Fixed bug with the ‘Wait for apply’ action not working correctly for free accounts (caused by the global queue)
  • Fixed bug with pipelines not marking actions as disabled when cloning
  • Fixed bug with browsing paths in the ‘Deploy to AWS S3’ action (paths different than root were not being listed properly). Shout out to Roland for pointing that out!


  • Docker upgraded to v17.09

Get started now

14 days of unlimited trial. No credit card required.