Blog

New Features

• Webhook logging – the webhooks that you receive from your Git provider are now logged in the Repository tab of the project options. This option is especially useful when diagnosing why your pipelines are not triggering despite pushes to the selected provider.

Improvements

• [Upload to SFTP] The transfer speed of large files to an SFTP is now 10 to 20 times faster (!)
• [Security] It is now required to confirm your email before accessing the workspace and pushing code to Buddy Git hosting
• The invoker for executions triggered with pull requests in automatic mode is now being set properly
• When accessing Buddy via GitHub or Bitbucket, your username will now be the same as in your Git provider account
• Webhook response logging - until now, only the sent payload was saved. From now on, Buddy also logs body and headers of the provided response

New Features

• Slack action now supports layout blocks

Improvements

• New variables for pull request-based executions: BUDDY_EXECUTION_PULL_REQUEST_BASE_BRANCH, BUDDY_EXECUTION_PULL_REQUEST_HEAD_BRANCH

Bugfixes

• Improved error handling if incorrect CRON is provided for scheduled pipelines
• Fixed display of events regarding changes to ENV VARs on the activity stream
• Docker image version select in build actions should now load faster

New Features

• New feature: Run Visual Tests on your website with Buddy CI/CD

Improvements

• Added support for password authorization in custom repositories on SSH
• You now need to enter the name of the pipeline when removing it
• You can now clone a pipeline from its settings view

Bugfixes

• Changing the authorization method from HTTP to SSH in custom repos did not clear the credentials – fixed
• Removed permission select for users with admin privileges in the bulk assignment window

Buddy is built around a couple of simple rules. The most important are:

1. Stability
2. Data security
3. Simple configuration
4. Speed

This week we focus on the last point with new trigger conditions for your actions and pipelines. For example, you can now configure your actions to build CSS only if there were changes in .saas files since the last execution.

New Features

• New trigger conditions for pipelines and actions:
  • Run only on specific day and hour
  • Run only if another pipeline in the same revison finished successfully

Improvements

• [Helm CLI] Support for new Helm versions
• From now on, you can display inactive pipelines on the Pipelines view. This is useful if you want to clear the cache or remove the inactive pipeline to save space

Bugfixes

• Fixed a bug with fixed project variables being parsed as settable if another settable workspace-level variable was using the same key
• Fixed a bug with the Track names in request path and request body must match error appearing in the Publish APK action
• Sandboxes in legacy accounts should now be launching properly

New Features

• [Buddy Enterprise] New application: AWS STS role assumption

Improvements

• Until now, all refs were fetched into the pipeline's filesystem. Now you can decide between fetching a specific ref or all refs
• Added variable key validation when executing a pipeline with a webhook
• Every member with pipeline management permissions can now import/export pipelines and manage pipeline folders
• When assuming a role in the AWS integration, you can now set the maximum role session duration

Bugfixes

• In some cases, errors when synchronizing custom repository were not saved. Fixed
• Passwords used for custom repository authentication are now properly encoded
• [Buddy Enterprise] If one of workers was unavailable, it was impossible to add a pipeline. Fixed