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.

New mobile version

Web development is a desktop thingie. You sit at your desk, sip coffee, and watch Buddy turn your code into beautifully crafted websites while you give an occasional poke to that Vault-Boy bubblehead you got when leaving your first job at the local burger joint.

Get started now

14 days of unlimited trial. No credit card required.