New Features

• New action: Flutter

Improvements

• [Buddy Enterprise] Current version requirements changed to 19.03.5 for Docker and 1.24.1 for Docker-compose
• [AWS CLI, Firebase, GC CLI, Heroku CLI, Netlify, Cloudformation] added the 'Environment' tab. From now on users can install additional tools and packages required for running the action
• [E-mail] From now on it is possible to set a sender of the e-mails sent via this action
• [Lighthouse] Added environment variable support for the 'Website URL' field

• Execution time for the 'Prepare Environment' step is now displayed

  Bugfixes

• There were issues with terminating executions during the 'Prepare Environment' step - fixed
• In some rare cases - if the pipeline was updated shortly after the execution, the changes were not applied - fixed

New Features

• New action: Helm

Improvements

• [2FA] Improved error management when turning on two factor authentication
• [YAML] Improved error handling for situations where 'Copy Files' and 'Run Next Pipeline' actions refered to a non-existent pipeline
• [YAML] Added individual parse logs for mutliple *.yml files in the .buddy directory
• [K8s apply deployment] Added variable resolving in the 'Source path' field
• [PHP] General action improvements

• [Build actions] Docker image dropdown menu has its tags properly sorted with semantic versions comming first

  Bugfixes

• [Download Actions] Pipeline space was incorrectly calculated when using this action, which caused users to receive filesystem limit error message - fixed
• [Buddy Enterprise] Users were unable to change the action timeout - fixed

AWS Lambda has become a powerhouse of software deployment. It encourages simple, self-contained, stateless functions that run themselves and eliminate a large portion of the traditional operational overhead that is associated with running software. Alas, many CI/CD tools have a lot of catching up to do before they're even close to the kind of ease that AWS Lambda offers.

Improvements

• Added support for Mac pre-OSX-based FTP servers
• Improved error display for 2FA login attempts
• Added workspace space consumption to the current usage section on the Billing tab

Bugfixes

• Fixed a bug with multi-line encrypted variables with empty lines causing incorrect encryption output
• [On premises] Fixed logs for the start times of microservices in build actions

Improvements

• The project status will now change if a pipeline is enqueued
• It is now possible to delete a pipeline even if it has been configured with YAML
• Upgraded Kubernetes client in actions
• Improved performance of webhooks sent from Buddy in the Web action
• Improved hiding of encrypted values for multiline variables in the action logs

Bugfixes

• [Build Docker Image] Skipping this action caused other actions that used the built image to fail - fixed
• [Git Crypt] & [Git Push] Fixed an issue that caused the actions to fail if the project contained submodules
• [Upload to WebDAV] Fixed a bug with the action failing if the uploaded folder contained a space character
• Starting too many services in a build action caused it to fail without providing any errors - fixed
• Fixed a bug with build actions in the On Failed section failing if action logs were too long

Improvements

• We have doubled the amount of tags that can be displayed with a date in the 'Run Execution' tab
• [REST API] Improved returning headers for rate limits
• Improved pipeline validation in pipeline settings

Bugfixes

• Fixed an issue with action update failing when adding a new microservice
• [SSH] Fixed the displayed error for not providing the key passphrase
• Switching between GUI and YAML modes while an execution was running caused the executions to multiply. We have locked the ability to switch between the two modes in such cases

The difference between Buddy and other CI/CD tools is that you can seamlessly add it to your existing setup with dozens of integrations. Right now, each integration is assigned to an individual user. One of the imnprovements we are currently working on is the ability to share the integration with other workspace members. During the works, we decide to change the ID's of the integrations from numerical to hash. This is important for users keeping pipeline configuration in YAML files as the ID defines which integration should be used in the action.

While lots of people think of CI/CD as something that lets developers deploy software faster and more frequently, let us not forget about its core principle: testing. Without testing, it is impossible to keep high standards of the code which constitutes the website. However, testing does not stop with deployment. Once our application is on the server, it should be constantly monitored for performance. Performance is one of the key factors that determine the position of the website in Google, the difference between life or death in online business.

For this, we can use Lighthouse, an open-source tool allowing developers to run performance audits on their websites. Buddy incorporates this tool as a dedicated action that you can use recurrently for round-the-clock coverage, or after every deployment to check the impact of changes on the website.