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.

Improvements:

• 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)

Bug fixes:

• [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.

New features:

• Build container access for services – from now on the main container of the build action is accessible for the microservices. You can set its hostname in the action’s ‘Services’ tab

Improvements:

• New ‘Code’ view for intergrated projects
• You can now import a synchronized repo from scratch in case of problems
• It’s now possible to allow empty values in the ‘Find & replace’ action
• Improved handling of errors in Kubernetes actions

Bug fixes:

• When deploying from the filesystem the files from the .git folder were displayed incorrectly in the changeset which was slowing down the deployment in case of large repositories. Fixed
• [Buddy Enterprise] Fixed a bug with adding the Sentry integration
• [REST API] Fixes in adding the Cloudfront action
• Minor fixes to the ‘Hugo’ action

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.

New features:

• Run E2E tests on your JavaScript apps with Cypress.io
• Monitor application stability with Raygun
• YAML patterns for pipelines

Improvements:

• 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

Bug fixes:

• 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.

New features:

• Version history for pipelines (available for admins in pipeline settings)

Improvements:

• [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 next_project_name and next_pipeline_name
• [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 source_project_name and source_pipeline_name instead
• [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: docker_build_action_name

Bug fixes:

• 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
• The remote_path in 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!