Improvements

• [Build actions] Added a possibility to grey out logs of commands/block of commands by using #region encrypted begin and #region encrypted end markers
• Integration ID's now use hash instead of numerical values. Check the article here if you are using configuration-as-code

Bugfixes

• "[Netlify] Fixed a bug with the 'Sites' dropdown menu not showing all available sites"
• "[Action logs] Fixed the greying out of encrypted variables with exceptionally long values"
• "[Clone pipeline] Cloning pipelines using API did not fetch the 'On failed' and 'Back to success' actions properly - fixed"
• From now on, the 'Recently failed' label will appear next to the appropriate action from the entire block of parallel action

New Features

• New action: Review performance, quality, and correctness of your apps with the Lighthouse audit tool

Improvements

• [Amazon S3] Improved action testing: we are now checking if the configured path exists in the bucket
• [HTTP Request] The action has been improved for performance
• Improved project status definition on the dashboard

Bugfixes

• [Azure] Fixed a bug with pushes to Azure being made to the pipeline branch instead to the pipeline set in the targetBranch field

New Features

• Download files from your remote server to the filesystem with three new download actions: FTP, SFTP & Amazon S3

Improvements

• [Discord] Added support for missing fields in attachments
• [REST API] Standardized codes and error messages returned by the REST API

Bugfixes

• Terminating a build action during the Customize Environment stage did not always work properly - fixed

Improvements

• New Docker registry in build actions: Other (Public)
• .NET Core actions now use the mcr.microsoft.com registry as default
• Added length validation for variables sent in pipelines executed with web hooks

Bugfixes

• [YAML] Fixed a bug with changing the name of the Docker build action throwing an error if other actions were using that image

Deprecations

• [Discord] Actions added before August 20, 2019, are now deprecated. Check out this article for instructions on updating them

Buddy is the official partner of Amazon Web Services with native integrations to many AWS services. This means you can use Buddy to automate deployments to EC2 instances, S3 buckets, ECS, or Elastic Beanstalk.

AWS services in Buddy

New features

• [AWS] Amazon integrations now support role assumptions

Improvements

• [REST API] Added error support if a wrong revision was provided on execution run
• [New Relic] It is now possible to set a custom application version
• [2FA] When activating 2FA you will be automatically logged out from all Buddy sessions except for the current one

Bugfixes

• [New Relic] Fixed a bug with the action failing if the pipeline trigger mode was set to NONE
• [REST API] Fixed a bug with changes to the pipeline trigger mode clearing ref_type and ref_name
• [REST API] Fixed a bug with execution fetch not working properly if the execution commit had been removed from the repository
• Fixed a bug with the commit status not being sent to Bitbucket if the pipeline name was longer than 26 characters

Environment variables (or ENV VARs) greatly expand the scope of things that can be achieved with Buddy. Although the most common use case is keeping sensitive configuration data safe and sound (server credentials, passwords, SSH keys, etc.), you can use them, for example, to:

• parameterize pipeline execution
• auto-increment application version
• pass parameters between actions or pipelines

New features

• You can now parse environment variables in commits

Improvements

• QR codes for 2FA now display user email in the authy application

Bugfixes

• Fixed a bug with spacebars in empty lines crashing the action if entered in the environment customization field
• Username and password in the Web action are now properly obfuscated
• Fixed a bug with Mount path in container not being copied when cloning build and Run Docker container actions