Blog

Buddy v2.2.17 Released (09-04-2019)
9 April 2019

Buddy v2.2.17 Released (09-04-2019)

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
Monitor application stability with Raygun
New feature: Run E2E Tests with Cypress.io
3 April 2019

New feature: Run E2E Tests with Cypress.io

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.

New feature: YAML patterns for pipelines
Buddy v2.2.16 Released (01-04-2019)
1 April 2019

Buddy v2.2.16 Released (01-04-2019)

New features:

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
New feature: Version History for Pipelines
28 March 2019

New feature: Version History for Pipelines

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.

Buddy v2.2.15 Released (26-03-2019)
26 March 2019

Buddy v2.2.15 Released (26-03-2019)

New features:

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!
New feature: Custom Services in Build Actions [Beta]
Buddy v2.2.14 Released (19-03-2019)
19 March 2019

Buddy v2.2.14 Released (19-03-2019)

New features:

Improvements:

  • 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

Bug fixes:

  • 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
Scheduled Server Upgrade [March 18-23]
15 March 2019

Scheduled Server Upgrade [March 18-23]

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 support@buddy.works 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

0