New action: Run tests in parallel

Testing is essential to keeping high quality of code. However, it can also prove very time-consuming if you run a large number of tests. To reduce testing time, we have introduced a new action that will let you split your tests in packages across several actions and run them in parallel.

Buddy v2.2.1 Released (12-02-2019)

New features:

  • It is now possible to run tests in parallel with the new ‘Split tests’ action


  • Added information about storage consumption in the workspace to Current Usage in the Billing tab

Bug fixes:

  • Fixed a bug with build actions having double variables after cloning
  • In some cases, the AWS CodeDeploy action was failing without returning any logs. The errors are now handled properly
  • A bunch of fixes to using previously built Docker images in build actions (e.g. action failing after clearing the cache)
  • Fixed a bug with the ‘Find & Replace’ action now working upon indicating a certain hidden file in the source path
  • Changing the workspace domain prevented custom Git projects from fetching changes in the repository due to authorization issues. Fixed
  • [REST API] Fixed a bug with using filters on branch and date simultaneously while downloading commits
  • [Buddy Enterprise] Fixed a bug with the ‘Copy files’ action not working on the standalone

Buddy v2.2.0 Released (05-02-2019)

New features:

  • New action: Gatsby CLI- build apps and websites with React with the new static site generator
  • Parallel actions are now available for all users, which marks the end of the Beta period. We have also increased RAM on the Starter plan to 3GB. Both changes do not affect currently selected plans – in order to use the new features, you need to upgrade your plan and accept the new pricing scheme


  • You can now define the bucket to which the application package will be deployed for the ‘AWS Elastic Beanstalk’ and ‘AWS CodeDeploy’ actions
  • It is now possible to set a custom commit message in the ‘Git Push’ action
  • In order to clear dangling images in the ‘Build Docker image’ action, docker image prune is executed by default. In certain multistage builds, some of the layers were always built without the cache. You can now switch off prune if required
  • The actions from the ‘Others’ section have been redesigned - from now on, ‘Pass arguments’, ‘Wait for apply’, ‘Copy files’, ‘Trigger pipeline’, ‘Find & replace’ and ‘Sleep’ have a more intuitive design
  • The trigger condition in build actions has been moved to a dedicated tab

Bug fixes:

  • Fixed a bug which caused that the SMS action wasn’t marked as failed although the daily limit has been exceeded
  • The keys added to the ENV VARs contained incorrect newline characters and therefore the keys in the OpenSSH format in some actions didn’t work right

Buddy v2.1.52 Released (29-01-2019)


  • [Google CDN] If there were more paths to validate, the user received the ‘Rate limit exceeded’ error. We have added additional 3 attempts in 1-minute intervals in case this error occurs
  • Encrypted value helper can now encrypt multiple-line variables

Bug fixes:

  • Fixed a bug with the YAML helper not receiving the list of the variables in the ‘Run next pipeline’ action
  • [REST API] Adding a new project variable resulted in adding it to workspace variables - now it is added properly
  • Fixed a bug which caused a build failure if the commit author didn’t accept Buddy invitation before
  • Minor bugs in the Rest API have been fixed

Buddy v2.1.51 Released (22-01-2019)

New features:


  • Show variables in logs
  • The variables in the ‘Run next pipeline action’ are now sorted in alphabetical order

Bug fixes:

  • Browse option in the remote path for the SFTP and Rsync actions has been fixed
  • Fixed a bug which cleared the private key while editing Rsync action
  • When settable variables were empty while defining a build action, they weren’t exported correctly to subsequent actions - now they are exported correctly
  • Fixed a bug where in some cases the commit dates in $BUDDY_EXECUTION_CHANGELOG variable were incorrect

New SSH implementation

SSH keys are rightly considered the more secure method of authentication as compared to traditional user/password method. To maintain the high-security level of our service, we have upgraded the SSH library in Buddy to support the Ed25519 format.

Along with these changes, we have performed an internal audit resulting in moving the whole infrastructure to the more secure SSH standard.

New action: Deployment to UpCloud

In response to the already huge number of requests from our users, we’re happy to deliver a dedicated integration with the UpCloud hosting services

UpCloud provides cloud infrastructure renowned for its high-performance, scalability and friendly approach towards developer needs. You can find the new integration in the IaaS section of Buddy’s actions:

Buddy v2.1.48 Released (15-01-2019)

New features

  • New integration: Deployment to UpCloud
  • New SSH implementation – the new library allows for new types of keys in Git authorization and SSH/SFTP actions
  • Variables in REST API – from now on you can manage your Workspace/Project/Pipeline variables via the API


  • New Default Variable: $BUDDY_EXECUTION_CHANGELOG
  • New Default Variable: $BUDDY_EXECUTION_PULL_REQUEST_NO. Contrary to $BUDDY_EXECUTION_PULL_REQUEST_ID which produced the PR name as pull/[number], the new variable only contains the number
  • [AWS] By default, the AWS S3 action sets the MIME type of uploaded objects. It is now possible to disable this feature
  • [SSH] When executing commands on a server with the SSH action in the script mode, Base64 is required on the server. Buddy will now validate it before the execution
  • [UI/UX] Improved forms for adding/editing action — fixed issues with browser autofill and remembering password modals


  • [Docker] Adding two Docker build actions and setting them in parallel was resulting in a failed execution. Fixed
  • [Docker] Fixed a bug with the flag ‘Allow connection to insecure registry’ wasn’t working properly for all URLs in the ‘Push Docker image’ action
  • [Trigger conditions] Fixed a bug with ENV VAR trigger conditions not working in pipelines whose branch assignment is set to NONE
  • [Docker] Using ENV VARs in the source path in the ‘Push Docker Image’ action was casuing with incorrect path. Fixed
  • [Buddy Enterprise] Improved Azure application and ontegration support for all K8s actions

Get started now

14 days of unlimited trial. No credit card required.