Buddy v1.5.47 Released
3 October 2017

Buddy v1.5.47 Released


  • Many users were reporting than monitoring actions are too ‘sensitive’. From now on, the action will try to connect 3 times until it’s marked as Failed
  • You can now select a single file to archive in the Zip action instead of a directory only
  • Deployment to AWS ElasticBeanstalk & AWS Code Deploy have been optimized for performance + the logs for both actions are now much clearer
  • You can now select the config file from the pipeline filesystem in Apply deployment to K8s and GKE actions
  • The commit input in the file editor now supports CTRL+C/CMD+C


  • Fixed bug with commits from external repositories not synchronizing correctly because of special characters in the name
  • Fixed bug in the AWS S3 action with incorrect path invalidation if both ‘cloudfrontId’ and Buddy parameters in the ‘RemotePath’ were provided
  • Fixed bug with Zip action not packing files and directories starting with .
  • Fixed bug with wrong files getting uploaded to the server because some ignore paths in the Rsync action were not working correctly
  • Fixed bug with errors showing for some server certificates in the Web Monitoring action
File types in the Filesystem
29 September 2017

File types in the Filesystem

One of the most important components of pipelines is the filesystem: a reserved disk space with a clone of your repository, where Buddy installs dependencies, merges & compresses the assets, and generates artifacts.

With this week’s release we’ve added a UI distinction for three types of files and folders in the filesystem:

Buddy v1.5.46 Released
26 September 2017

Buddy v1.5.46 Released

New features

  • Artifacts and static files are now marked with a special icon in the Filesystem. This way you can easily see which files have been created or processed by build actions, which are the same as in the repository, and which have been manually uploaded to the filesystem


  • From now on password reset and invite URL’s have a live time value set to 24h and 7 days respectively
  • You can now set no_skip_to_most_recent flag in YAML and API configuration. Normally, if there’s more than one execution queued for 1 pipeline, only the newest one is run and the rest is skipped. This option lets you force all executions one by one
  • Heroku CLI action can be now run pipelines with branch assignment set to ‘None’
  • Website monitoring now ignores certificate errors. This means you can now monitor staging websites with self-signed certificates\
  • Added invoice number to the Billing tab. The number has replaced the issue date as the URL to the invoice


  • SSH keys defined in build actions were being uploaded to /root/.ssh directory by default. Since a user doesn’t have to be the root in the container, the keys are now uploaded to ~/.ssh directory


  • Slack service library upgraded to v1.5.1
  • Lockback service library upgraded to v1.2.3
  • [Enterprise] buddy/front base image upgraded from node:6.11.1-alpine to 6-alpine
  • [Enterprise] buddy/redis base image upgraded from redis:3.2.8-alpine to 3.2-alpine
  • [Enterprise] buddy/mongo base image upgraded from mongo:3.4.2 to 3.4
  • [Enterprise] buddy/mariadb base image upgraded from mariadb:10.1.21 to 10.1
  • [Enterprise] buddy/haproxy base image upgraded from haproxy:1.5.18-alpine to 1.5-alpine
  • [Enterprise] buddy/utility base image upgraded from golang:1.6.2-alpine to 1.9-alpine
  • [Enterprise] buddy/utility-update base image upgraded from golang:1.6.2-alpine to 1.9-alpine
  • [Enterprise] buddy/sandbox-routing base image upgraded from node:6.10.2-alpine to 6-alpine
Pipeline of the Week: Angular > Webpack > Magnolia by Neoskop
New action: GCC Compiler
20 September 2017

New action: GCC Compiler

We’re happy to announce that Buddy now officially supports GCC.

GCC, or the GNU Compiler Collection, lets developers to compile applications written in C, C++, Objective-C, Fortran, Ada and Go (to which we already have a dedicated action), alongside libraries for these languages.

New action: ZIP Files
19 September 2017

New action: ZIP Files

For your convenience, the popular command is now available as a separate action.

Invented by Phil Katz in the 80’s, Zip has been an inseparable part of IT for almost 30 years, with even your mom zipping those family photos to reduce the size of the attachment before sending them over Gmail.

Buddy v1.5.44 Released
19 September 2017

Buddy v1.5.44 Released

New features


  • Artifacts and files uploaded manually are now marked respectively marked in the pipeline filesystem
  • It is now possible to set auto_clear_cache in YAML and API configuration. This way every execution will run without the cache
  • You can now use a pattern to exclude files in the Deploy Lambda Function action
  • {validate} flag has been added to K8s/GKE Apply Deployment with the default value set to true
  • Improved list of pipelines with more focus on branch and trigger mode. The changes make it easier to locate the desired pipeline


  • Fixed bugs in build trigger conditions that decide if the action is to be executed or skipped in a given execution:
    • cloning actions between pipelines did not transfer trigger conditions
    • executions triggered by users with custom permissions in the project did not include trigger permissions; as a result, the actions were triggered on every time
  • Fixed bugs in the HTTP Request action
    • action test did not include environment variables
    • added support for HTTP authorization in YAML configuration
Announcing: New Build Servers & Infrastructure Upgrade
13 September 2017

Announcing: New Build Servers & Infrastructure Upgrade

Before we started working on Buddy in 2015, we made an analysis to indicate the user needs and the best niche for our application.

We worked out 3 selling points that were to become the foundations of Buddy:

  • speed and stability (essential in Continuous Integration and Delivery)
  • ease of configuration/integration with other tools
  • outstanding UI/UX

Since development of Buddy is 100% customer driven, we did change our approach to some things in the past two years. However, we have never stepped an inch away from any of these policies. Such approach allowed us to grow and win recognition of web and software developers.

Buddy v1.5.43 Released
12 September 2017

Buddy v1.5.43 Released


  • New server infrastructure for build actions
  • Due to an issue with Docker image layers were not being properly removed when cleaning dangling images, which was causing disk usage to grow uncontrollably. Upgrading Docker has solved that problem
  • Improved action review when manually triggering the pipeline
  • It is now possible to send HTML in email notifications
  • Short revision added to Buddy parameters
  • Added Always run all queued executions flag to YAML


  • During the last couple of weeks some of our users were reporting that if a branch is removed from the repo it remains assigned to the pipeline, which was causing the Pipelines view to crash. Fixed
New feature: Private Docker images in builds
7 September 2017

New feature: Private Docker images in builds

Last year we added a feature that lets you build and test your applications before the deployment. We decided to use Docker containers for that, an approach that has many advantages:

  • All builds are isolated in separate containers
  • It’s very easy to define your own Docker image (build environment)
  • You can use existing Docker images created by the Docker community

Basing on the feedback from our users, several months later we added an option to build custom images and push them to private repositories, with dedicated support for public Docker Hub, Google Container Registry, and Amazon EC2 Container Registry.