Raygun is a monitoring software which enables developers to track their deployments and application stability. Raygun integration with Buddy will allow you to monitor, diagnose and quickly debug issues to deliver flawless applications.
Cypress is a fast and easy to use test runner for front-end apps, featuring a number of options that help developers comprehensively test modern websites. The new integration allows you to automatically run tests on every change to code, recurrently on an interval, or on manual pipeline execution.
Two years ago we introduced configuration-by-code to Buddy. The feature allows you to change pipeline configuration simply by updating a YAML file and commmitting it to the repository.
Today, in response to numerous requests from our users, we’re adding the option to define multiple pipelines with one definition.
- Monitor application stability with Raygun
- YAML patterns for pipelines
- Ignore paths now support ENV VARs
- In case of connection problems when pulling an image from the Docker Hub, Buddy will try 3 times before marking the action as failed
- If paths in the additonal cache were ending with a directory of the same name, they were cached incorrectly. Fixed
- Fixed a bug with deleting variables with the Rest API
- Fixed a bug with installing Helm in Kubernetes actions
The core principle of Continuous Delivery is to version everything and everywhere: not only the source code, but also things like configuration files or SQL’s used for database migration. In 2017, we introduced YAML configuration for pipelines, enabling you to store pipeline configuration in the repo as
buddy.yml. This way developers could easily track the changes to their workflow.
Today we add the option to browse pipeline history in projects configured with the GUI.
- Version history for pipelines (available for admins in pipeline settings)
- [HTTP action] The log now contains the URL address and the payload
- [Run next pipeline in YAML] From now on you don’t need to know the ID of the pipeline that you want to run. Instead, you can define
- [Copy files in YAML] From now on you don’t need to know the ID of the pipeline from which you want to copy files. Instead, you can define
- [Build/Run Docker Container in YAML] If you want to use the previously built image, just enter the name of the action in which it was built:
- Authorized apps in my-ID are now loading faster
- Fixed a bug with the Elastic search microservice in versions lower than 3.0.0 not starting properly
remote_pathin the Google CDN action couldn’t be set in the REST API and in YAML. Fixed
- If the payload of the ‘HTTP’ action or the attachment in the ‘Slack’ action contained a variable with newline characters, the JSON sent was incorrect. Fixed
- Fixed a bug with parallel actions using different images causing errors in the executions
- Fixed a bug with recovery codes not working for turning off 2FA. Thanks for pointing that out, Aubrey!
Building and testing applications are the core features of Buddy, right alongside deployments. In order to test your app properly, however, you often need a database or some other service. Buddy handled that with predefined services like MySQL, PSQL or MongoDB. Until now.
- Custom microservices in build actions [Beta] – run parallel tests for frontend and backend, or add your own custom database
- It is now possible to change the workspace owner in the workspace preferences
- You can now enter the path prefix at the ‘Purge everything’ option in the AWS CloudFront action
- From now on, you can use ed25519 keys with a passphrase in the SSH/SFTP actions
- Notification actions have been redesigned for better
- Fixed a bug with GitHub repositories not synchronizing correctly if they contained 1000+ pull requests
- In some cases, pipelines with the ‘Terminating’ status were blocking the global execution queue in the workspace. Fixed
Dear developers, From March 18 to March 23 we will be upgrading the system on our build servers. There will be no downtime whatsoever, but some of the pipelines might be temporarily run without the cache, which will prolong the execution time.
The slowdown may happen only once per pipeline, and concerns only 20% of all our users.
If you wish, you can reach out to us on email@example.com or on the live-chat, and send the URL to your account – we’ll check if your workspace is among those 20% and send you the list of pipelines that may be affected.
Thank you for understanding and sorry for possible inconvenience.
You can subscribe to automatic notifications on the status of our servers on our Status Page
“Clean”, “intuitive”, “easy to use” – Buddy’s UI is probably the most praised feature of the service, which makes us extremely proud. Of course, it’s not about bells & whistles just for the sake of it – every single element has been carefully crafted to help developers introduce CI/CD with as little effort as possible.
However, we’ve been adding new features for so long now that the time has come to clean up the house and move some furniture.