Buddy v2.1.25 Released (11-09-2018)


  • [Datadog] You can now choose NA and EU region
  • [AWS CLI] We’ve added a possibility to choose between BASH and SH shell what allows you to execute more advanced scripts
  • [AWS] Improved error handling in CloudFront and Amazon actions

New database options (MySQL, Postgres, MariaDB)

Buddy is a smart tool that lets you build and deploy your web projects. Before the application is deployed to the server, however, it is first tested in preconfigured Docker containers. Some of the tests, e.g. integration, E2E or Selenium, require a fully operational application with things like a database and session storage.

Buddy supports this functionality with microservices activated in build actions:

Buddy v2.1.24 Released (04-09-2018)

New Features

  • New options in database services (MySQL, Postgres, MariaDB): it is now possible to seed databases and create the default database when starting up the service


  • By default, Heroku and Git Push actions make a push to the specified remote with the --force flag applied. You can now turn the flag off in ‘More Options’ of both actions
  • AWS Elastic Beanstalk & AWS CLI now use Ubuntu 18.04 with Python 3.6 installed (upgraded from 16.02 and Python 2.7). This has solved issues with coding special characters


  • Improved service of new line in attachments in the Slack action

New feature: Build and run Docker containers on AWS ECS

We’re happy to announce that Buddy now supports deployments to the AWS ECS! Amazon Elastic Container Service is a scalable container orchestration service that lets you run Docker containers on the Amazon infrastructure.

With Buddy, you can easily create a delivery pipeline that will dockerize your application, push it to the ECR registry, and launch it on the ECS:

Buddy v2.1.22 Released (28-08-2018)

New Features

  • You can now build and run Docker images on AWS ECS with Buddy CI/CD


  • In the previous release we added kubectl version select for K8s actions. This is now supported by both the API and YAML.
  • Indexes and inquires to DocumentDB have been optimized to increase the speed of the Activity stream
  • [Security] The key exchange mechanism diffie-hellman-group1-sha1 has been removed due to vulnerability issues


  • Fixed a bug with defining recurrent pipelines using a crone string through the API/YAML

New feature: selecting kubectl version

Buddy turns delivery to Kubernetes into a breeze. In a couple of minutes you can configure advanced pipelines that will test and build your application into a Docker image, push it to the registry, apply deployment, and run job in your K8s clusters.

Communication with K8s clusters is performed with the Kubernetes command-line tool, kubectl. The version used should always be compatible with the version installed on the server.

Buddy v2.1.21 Released (21-08-2018)


  • [Kubernetes] You can now choose the kubectl version which will be used for automation in all K8s actions
  • It is now possible to define title and description in the ‘Pass arguments’ action


  • [Sentry] Fixed a bug with refresh token causing errors in the Sentry action
  • [Run kubectl CMDs] Fixed a bug with sending the project name instead of the project ID In the ‘Service account’ authorization.
  • Resetting the password didn’t work for logged users because the token link was expiring immediately after logging in. Fixed

Possible limitations due to the Docker Hub's maintenance (August 25, 2018)

Due to planned maintenance on Docker Hub, Docker Cloud, and Docker Store on Saturday, August 25th, 2018 at 11 am PT, Buddy’s functionality may be temporarily limited.

Limitations may include build actions and other actions run in Docker containers, such as ZIP or ElasticBeanstalk. According to Docker Hub, the downtime will take 45 min. max.

You can read more about the downtime here: https://success.docker.com/article/planned-downtime-on-hub-cloud-store

Sorry for the inconvenience.
The Team at Buddy

Introducing: API-parameterized executions

When we develop new features, we try to keep things simple, yet with no compromise to flexibility. A couple weeks ago we delivered parameterized builds. Although it was met with very positive feedback from the community, some users missed the option to parameterize executions via the API as well.

This option has just been delivered: from now on, you can run a pipeline via the API and pass the parameters that will be available in all actions.

Get started now

14 days of unlimited trial. No credit card required.