Blog

On Wednesday, September 16, we held our first webinar on our YouTube Channel. The webinar covered delivery automation of React applications with special emphasis on zero-downtime deployment, followed by a Q&A section in which we answered questions from the community.

Improvements

• It is now possible to set the default 2FA method if both application and SMS is selected
• You can now run executions with parameters using Slack slash commands

Sandboxes 2.0

• Added support for Ubuntu 20.04

Bugfixes

• Fixed a bug with Immediate flag in the Ghost Inspector action causing the action to fail
• Fixed a bug with logs in the SSH action stopping on Resolving host even though all remaining commands have actually passed
• Fixed a bug with the Approve button not working in the Wait for approval action if the trigger condition was set to changes to specific paths and the execution was set to upload everything to scratch

New Features

• Introducing: Buddy 2.0 Design – Workspace and People tab

Improvements

– [Buddy On-Premises] The Workers tab now displays the list of pipelines assigned to a given worker

Sandboxes 2.0

• The Usage tab in workspace settings now display the list of active sandboxes
• Added confirmation when closing the Terminal tab
• Removed pipeline creation button in for projects with YAML configuration

Bugfixes

• The date of the next charge is now properly displayed in the My-ID tab
• Integration ID is now properly displayed on the integration dropdown in the action details
• Variables with Pipeline scope are now properly displayed in the Pass variables section of the execution run view

Dear beloved,

We are preparing to launch a new major release of Buddy. We’ve taken our best ideas that piled up from years of customer insights and feedback, and put together the best version of Buddy we’ve ever made.

The release of the new version will be performed in stages. First, we need to make some updates to the UI to clean up and make space for the new modules (yikes!). There will be a few iterations of the user interface before it will reach its final form of what we call Buddy 2.0.

New Features

• New action: Google Cloud Run

Improvements

• You can now pass variables to services attached to build actions
• Dockerfile Linter now supports YAML files with ignores
• [YAML] You can no longer add or edit actions using private integrations of other users in the same workspace
• [YAML] You can no longer add or edit actions with integration_id. We recommend using integration_hash instead.

Sandboxes 2.0

• It is now possible to clone a Sandbox from an existing one (previously only from snapshot)
• Restoring sandboxes from snapshots is now faster

Bugfixes

• Fixed a bug with some password managers suggesting Buddy credentials in the services password input
• Fixed a bug with updating Cloudflare integration from token to API key not working properly
• Added size validation to secret when adding or editing webhooks
• Fixed a bug with Pass variable displayed on the Run execution view for users who did not have pipeline management permissions
• Fixed a bug with personal access token returning old token during the creation if the scopes were the same
• Fixed a bug with Ghost Inspector action not failing even though the tests have failed, too
• Fixed a bug with Run Docker image action not using the variables set in the action
• Fixed a bug with 404 error on the repository Browse view if no commit was assigned to any branch

Alongside builds and tests, actions based on the SSH protocol remain one of the most favored features of Buddy. The most popular use cases include:

• Deployment – the SSH protocol is used to connect and upload files to an SFTP server
• Download from server – same as above, but the files are downloaded from the server to the filesystem
• Running commands on remote – users connect to the server and use the SSH protocol to run commands

Environment variables are pairs of keys with dynamically named values. You can use them in Buddy's pipelines in a variety of ways, for example:

1. To store sensitive data required in the delivery process which cannot be stored in the repository for security reasons.
2. To pass values from one pipeline action to another with settable variables.
3. To pass values that vary from execution to execution, such as the version number.

New Features

• You can now set up a proxy in the [SSH] and [SFTP] actions
• It is now possible to change the value of the variable sent to the execution or to add new variables when running a pipeline

Improvements

• Invitation to workspace now contains the name of the inviting person
• [Visual tests] Added support for sending headers to the tested website and variables in the URL input
• [Buddy On-premises] From now on, you can allocate RAM via the GUI in the standalone's Settings tab
• The Target website URL field in the pipeline now supports ENV VARs
• You can now add the Cloudflare integration using a token, not a global API key
• Optimized tags/refs listing on the Run execution view
• Added validation to SSH keys

Bugfixes

• [SSH action] Variables with the same name defined both on pipeline and on project level sometimes took the value of the project instead of the pipeline. Fixed
• Fixed a bug with terminating an execution of a pipeline with the Run next pipeline action not producing logs for this action
• Fixed a bug with the timeout error resulting in the 'terminated' status instead of 'failed'

With this week's update we deliver one of the most requested features: the ability to debug errors directly in the pipeline.

Buddy lets you run tasks and commands in isolated containers with preinstalled frameworks and dependencies. When a build fails, it produces logs that you can use for debugging. However, sometimes the logs are not enough and the best method is debugging the error directly from the terminal. Now, you can launch such terminal in build containers from Buddy's UI with no additional configuration (such as with SSH keys).