10 December 2019

Buddy v2.2.72 Released (10-12-2019)

Buddy v2.2.72 Released (10-12-2019)

Improvements

  • We have doubled the amount of tags that can be displayed with a date in the ‘Run Execution’ tab
  • [REST API] Improved returning headers for rate limits
  • Improved pipeline validation in pipeline settings

Bugfixes

  • Fixed an issue with action update failing when adding a new microservice
  • [SSH] Fixed the displayed error for not providing the key passphrase
  • Switching between GUI and YAML modes while an execution was running caused the executions to multiply. We have locked the ability to switch between the two modes in such cases
6 December 2019

Feature update: YAML integrations

Feature update: YAML integrations

The difference between Buddy and other CI/CD tools is that you can seamlessly add it to your existing setup with dozens of integrations. Right now, each integration is assigned to an individual user. One of the imnprovements we are currently working on is the ability to share the integration with other workspace members. During the works, we decide to change the ID’s of the integrations from numerical to hash. This is important for users keeping pipeline configuration in YAML files as the ID defines which integration should be used in the action.

Numerical ID’s will be suported for two more months. From February 2020 onwards, adding new or modifying existing actions will require the new type of ID.

4 December 2019

New feature: Audit website performance with Lighthouse

New feature: Audit website performance with Lighthouse

While lots of people think of CI/CD as something that lets developers deploy software faster and more frequently, let us not forget about its core principle: testing. Without testing, it is impossible to keep high standards of the code which constitutes the website. However, testing does not stop with deployment. Once our application is on the server, it should be constantly monitored for performance. Performance is one of the key factors that determine the position of the website in Google, the difference between life or death in online business.

For this, we can use Lighthouse, an open-source tool allowing developers to run performance audits on their websites. Buddy incorporates this tool as a dedicated action that you can use recurrently for round-the-clock coverage, or after every deployment to check the impact of changes on the website.

3 December 2019

Buddy v2.2.71 Released (03-12-2019)

Buddy v2.2.71 Released (03-12-2019)

Improvements

  • [Build actions] Added a possibility to grey out logs of commands/block of commands by using #region encrypted begin and #region encrypted end markers
  • Integration ID’s now use hash instead of numerical values. Check the article here if you are using configuration-as-code

Bugfixes

  • “[Netlify] Fixed a bug with the ‘Sites’ dropdown menu not showing all available sites”
  • “[Action logs] Fixed the greying out of encrypted variables with exceptionally long values”
  • “[Clone pipeline] Cloning pipelines using API did not fetch the ‘On failed’ and ‘Back to success’ actions properly - fixed”
  • From now on, the ‘Recently failed’ label will appear next to the appropriate action from the entire block of parallel action
27 November 2019

Buddy v2.2.69 Released (27-11-2019)

Buddy v2.2.69 Released (27-11-2019)

New Features

  • New action: Review performance, quality, and correctness of your apps with the Lighthouse audit tool

Improvements

  • [Amazon S3] Improved action testing: we are now checking if the configured path exists in the bucket
  • [HTTP Request] The action has been improved for performance
  • Improved project status definition on the dashboard

Bugfixes

  • [Azure] Fixed a bug with pushes to Azure being made to the pipeline branch instead to the pipeline set in the targetBranch field
21 November 2019

New feature: Download files from remote server to filesystem

New feature: Download files from remote server to filesystem

Obsessed with making CI/CD as easy as possible, in the past couple of years we delivered a series of actions allowing developers to automate application delivery in a couple in minutes rather than hours. However, Continuous Delivery is not limited to uploading files to the server. The essential part of the process is testing every commit and building the application before the deployment. Sometimes these steps require files which shouldn’t or cannot be stored in version control, such as configuration files or database dumps required to run tests.

19 November 2019

Buddy v2.2.68 Released (19-11-2019)

Buddy v2.2.68 Released (19-11-2019)

New Features

  • Download files from your remote server to the filesystem with three new download actions: FTP, SFTP & Amazon S3

Improvements

  • [Discord] Added support for missing fields in attachments
  • [REST API] Standardized codes and error messages returned by the REST API

Bugfixes

  • Terminating a build action during the Customize Environment stage did not always work properly - fixed
12 November 2019

Buddy v2.2.67 Released (12-11-2019)

Buddy v2.2.67 Released (12-11-2019)

Improvements

  • New Docker registry in build actions: Other (Public)
  • .NET Core actions now use the mcr.microsoft.com registry as default
  • Added length validation for variables sent in pipelines executed with web hooks

Bugfixes

  • [YAML] Fixed a bug with changing the name of the Docker build action throwing an error if other actions were using that image

Deprecations

  • [Discord] Actions added before August 20, 2019, are now deprecated. Check out this article for instructions on updating them