Blog

New features

• New action: DigitalOcean CDN
• [Custom services] New option: Wait for custom service daemon on specified port – [REST API] It is now possible to clone and export pipelines from your projects

Improvements

• The list of executions now displays the total execution time
• Execution details now display execution time for each action
• Activity streams now display the YAML of the deleted pipeline
• Improved error support in environment preparation
• Adding group users to projects has been optimized
• Trigger condition on paths now supports environment variables
• [Telegram] It is now possible to send file attachments from the filesystem
• [Email notification] It is now possible to send file attachments from the filesystem (max 10 MB)
• [Discord] It is now possible to send multiple attachments from the filesystem (previously the limit was 1)
• [ZIP] If the target path does not exist in the filesystem, it will be created during the execution
• [Buddy Enterprise] The limit of services in build actions has been increased to 20

Improvements:

• Added request limit to invalidation actions (AWS CloudFront, CloudFlare, Google CDN). From now on, if the number of files sent for validation is higher than the set limit - all the files will be invalidated.
• Added the support for multiline comments in the executions
• Users can now change the ‘Run next action parallel’ flag in the action settings

Improvements:

• [Custom Services] Added more detailed logs in case the service has failed to start
• [Firebase] You can now select the version of and Node and Firebase CLI in the action details

Bug fixes:

• [Git Push] Fixed a bug with the ‘Git Push’ action failing if the commit message contained certain special symbols
• [AWS ECR] Pushing an image to a registry with a large number of repositories (>100) is no longer causing issues
• [Google Cloud Storage] Fixed a bug with cache control not being generated in the YAML generator
• Users will no longer encounter errors when pushing a repository via HTTPS
• Users will no longer encounter errors when opening an empty file during repository browse
• Fixed a bug with deleting an action causing errors if the action was in parallel mode
• Users with 2FA enabled were not asked for the authorization code when resetting the password - fixed

Continuous Integration and Delivery is all about simplicity. It’s not about configuring the process just for the sake of it—it’s about stripping it down to the bare minimum and adding new steps only if necessary. This approach guided us during Buddy’s development – to create a tool simple enough for every developer to embrace automation and expand the process at any point. It also applies to the very first step, which is setting up an account: a task that defines the whole user experience onwards.

New guide

• Learn how to dockerize and test a PHP application on every change to code

Improvements

• [Wait for approval] You can now see who and when approved the execution in the action logs
• [Copy files] Improved display of the pipeline’s source for users who don’t have access to it
• [Run next pipeline] Improved display of the pipeline to execute for users without appropriate permissions
• [Copy files] It is now possible to copy hidden files
• Improved error handling when synchronizing GitHub projects
• Improved error handling when selecting a path on the remote server
• Improved VAT-ID validation

Bug fixes:

• [Copy files] Fixed a bug with the action failing if it was executed by a user without permissions to the source pipeline
• [Telegram] It was possible to send a notification without any content which caused the action to fail. We have added a validation to prevent it
• [Cloudflare] Fixed a bug with the base URL getting inappropriately overwritten after loading zones

Improvements

• From now on, you can specify which ACL you want to set for files uploaded in the S3 action

Bug fixes:

• Fixed a bug with empty lines in build action commands resulting in an error during pipeline import
• If a pipeline was in a folder, cloning it between projects caused errors - fixed

Docker flows through the veins of Buddy. It is the fuel that makes our builds run so smooth and simple:

• First, it launches an isolated container.
• Second, it downloads dependencies and caches them in the pipeline’s filesystem mounted to the container.
• Third, it runs build commands on repository files.
• Fourth, it exports the artifacts to the filesystem nad kills the container.

By default, Docker containers are run with the user defined in the image. However, some of you were requesting an option to change the user – and this is what we are delivering this week.

New features

• You can now change the default user in build actions

Improvements

• Attempting to execute commands in the Bash shell in an image without Bash installed returned a wrong message. We have added a hint suggesting to switch to SH instead
• The capacity of the ‘Container CMD’ field in the custom services has been extented to 1000 characters

Bug fixes:

• Repository synchronization errors are now properly displayed
• In some rare cases, users were charged VAT despite a valid VAT-ID provided - fixed
• Fixed an issue where Buddy Enterprise users could not add the ‘Ghost Inspector’ action to their pipelines

Improvements

• If user did not provide any company details, the invoice will display the owner’s name
• Improved hostname validation of microservices in build actions
• Improved handling of cache invalidation actions
• From now on, the Gradle action will use the official Docker Hub Gradle image

Bug fixes

• It was impossible to delete an integrated project if the user had no administrative rights at the repository provider – fixed
• Fixed timeout support for the ‘Web’ and ‘HTTP Request’ actions
• Fixed an issue where testing an action configured via YAML did not work properly
• Firefox input support (e.g password) has been improved

Improvements:

• Improved support for clone/fetch of custom repositories
• Reduced waiting time in the Elastic Beanstalk monitoring action
• Symlinks are now listed in the remote path browser
• Added support for environment variables in the ‘Question’ field of the ‘Wait For Apply’ action