Buddy offers a dedicated set of actions allowing you to send deployment details to your favorite monitoring service. One of the most popular tools is Datadog, now complemented with an individual action which updates the service with the status of the build after the execution.
- Improved support of variables during the action testing
- VAT information is now displayed in the billing tab
- Fixed an issue where pushing changes to YAML configuration while the pipeline was still in progress stopped the pipeline from being run on push
- The link to the execution triggered by the ‘Run next pipeline’ action is now properly displayed in the action’s execution details
- If creating a folder during the deployment failed, the second attempt was always failing. Fixed
- Slack attachments will now properly support variables with new lines
- You will no longer see two confirmation notifications when deleting a project
- Fixed a bug that did not allow to select the free plan during the trial period
Ghost Inspector is a tool for an automated testing and monitoring of your website or application. Ghost Inspector runs the tests in a browser to mimic the user experience and ensure that everything is running as it should.
- Fixed an issue with the ‘Test Action’ not providing correct values for ENV VARs in notification actions
- Improved support of large logs in actions
- You can now use ENV VARs in the ‘Package Name’ field of the Google Play action
- The ‘Copy Files’ action will no longer fail if the filesystem of the source pipeline is empty
- Improved handling of Slack slash commands if provided parameters include capital letters
The ‘Pass arguments’ action in Buddy lets you ask about parameters during pipeline execution. The parameters are available in consecutive actions as environment variables. This way you can change the behavior of a pipeline while an execution is in progress.
- New action: Datadog status check
- New action options: Pass Arguments
- Added logs for microservices
- Fixed an issue when deleting an integrated project was causing a crash if Buddy did not have rights to delete webhooks
- Added default value for variables in the ‘Pass Arguments’ action
- Added info to the execution whether the pipeline was run with the API, Slack command or webhook (all three were marked as ‘manual’ before)
- Fixed a bug with ENV VARs in the
ApiKeyfield of the ‘Bugsnag’ action not getting resolved correctly.
- The Deploy from scratch option didn’t work correctly when the ‘Wait for apply’ action preceded the deployment action – fixed
- [Buddy Enterprise] Fixed a bug with the number of parallel actions not changing upon setting them via
As the majority of Buddy clients use an external Git provider, we have decided to give the Code tab an overhaul and gather all repository management options in one place, together with some additional info. This is a part of a wider operation in which we’ve been updating Buddy’s UI to better accommodate new features and changes.
- Following up the recent design changes to deployments, we have updated the UI of all remaining actions
- Actions configured with YAML can now be accessed in the GUI. You can also introduce changes and generate a new YAML for specific actions directly in the GUI
- You can now see the sent message and its attachments in the logs of the Slack action
- Improved error logging in Azure Kubernetes actions
- Added support for new regions in the AWS actions (Stockholm, Beijing, Ningxia)
- [Buddy Enterprise] Fixed a bug with builds using the previously built Docker image not working
- Fixed a bug with cluster data not loading correctly upon changing the Kubernetes provider in the ‘Set image’ action
Services in build actions are a very popular feature allowing you to test applications that require, for example, a database or a Selenium driver to run.
Three weeks ago we added custom services that enabled tests of microservice applications—a very similar feature to docker compose. Until now, the communication was limited to one side: you could connect to a database or another service from the container that was triggering the tests, but it was impossible to connect the other way back.
We’re happy to announce that connections now work both ways.