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.

Buddy v2.1.16 Released (31-07-2018)


  • [Android] It is now possible to deploy builds to Google Play with the ‘Internal test’ flag
  • [Kubernetes] The ‘Show-all’ flag in the get pods method is deprecated and no longer used in K8s actions


  • The Sentry action is now properly tested
  • Fixed escaping of special chars in the Slack notification content
  • Fixed desktop notifications in the ‘Wait for approval’ action

Introducing: Cron jobs in recurrent pipelines

As you probably know, pipelines in Buddy can be run in three ways:

  • Automatically on push
  • Manually on click
  • Recurrently on time interval

The last method can prove very powerful when properly put practice. For example, you can use it to monitor your servers or backup WordPress sites. However, the recurrent mode lacked advanced config settings, such as running the pipeline only on working days. We have addressed that by adding cron jobs to the pipeline settings.

Get started now

14 days of unlimited trial. No credit card required.