20 February 2020

New feature: Handling errors in actions

New feature: Handling errors in actions
The principle of Continuous Integration is simple: make changes > test for errors > integrate with code if everything is okay / fix bugs and test again if something's wrong. In Buddy, these tasks are performed by pipeline actions. If something goes wrong (e.g. the tests fail), Buddy will stop the pipeline and mark the responsible action as failed. One should never merge a branch with errors: this is an impassable rule that should never be violated and this is why we never allowed the pipeline to continue if an action was failing.
17 February 2020

Buddy v2.3.17 Released (17-02-2020)

Buddy v2.3.17 Released (17-02-2020)

New Features

  • Warning state in actions

Improvements

  • Added variable support for file attachments in notification actions
  • [Slack] You can now mention groups in the Slack action
  • [Email] Added email address validation
  • [Helm] You can now use the action without authorization to the K8s cluster
  • [Submodules] The environment preparation step in the pipeline's execution details will now be marked with the warning status if there was an error during submodule fetch

Bugfixes

  • [Lighthouse] If the min score was set to less than 10, the action was failing despite reaching a higher score. Fixed
  • Fixed a bug with pipelines in on push mode getting triggered in closed projects
13 February 2020

Introducing: Integration management scopes

Introducing: Integration management scopes
In response to popular (and long-drawn) demand, we're happy to announce that it is now possible to define the management scope of integrations with third party applications. Until now, only the integration owner could add and edit actions that required an integration. For example, if a company had an account on Amazon, only the user with the access data to that account could add actions with AWS services.
11 February 2020

Buddy v2.3.15 Released (11-02-2020)

Buddy v2.3.15 Released (11-02-2020)

New Features

Improvements

  • You can now provide exact paths to invalidate during the execution of CDN actions [CloudFront, Cloudflare, Google CDN, DigitalOcean CDN]
  • Improvements to the 2FA code entry window

Bugfixes

  • [YAML] Whenever a field has been deleted from the pipeline definition, the pipeline values were not restored to the default - fixed
  • [Services] Fixed a bug with builds not working properly if 'Persistent Storage' was selected in MySQL and MariaDB services
6 February 2020

Introducing: Workers for Buddy on-premises

Introducing: Workers for Buddy on-premises
Buddy CI/CD is available in two versions: cloud and standalone that you can install on your own server. Until now, the latter was restricted to one server per instance. With this week's release, you can install Buddy on multiple nodes connected in one instance to build, test and release your software faster. In other words, Buddy on-premises now supports workers.
5 February 2020

Release Android Bundles to Google Play store

Release Android Bundles to Google Play store

Buddy has been offering dedicated Android actions for some time now, allowing developers to base their entire delivery process on our platform. We understand how important it is to keep up-to-date with new tools and releases, that's why we are now introducing Android App Bundle support with two new predefined actions: Sign Bundle and Deliver Bundle to Google Play Store.

4 February 2020

Buddy v2.3.6 Released (04-02-2020)

Buddy v2.3.6 Released (04-02-2020)

New Features

Improvements

  • [YAML] Added support for *.yaml files
  • [Lighthouse] Added more checks to the action
  • Improved tag list loading time in build actions

Bugfixes

  • Whenever a build action used microservices and the hostname of the main container has been set to 'App' the build failed - fixed
  • [Apply K8s Deployment] If the provided config path did not exist, the action failed with no trace in logs - fixed
28 January 2020

Buddy v2.2.80 Released (28-01-2020)

Buddy v2.2.80 Released (28-01-2020)

New Features

  • New Buddy IP addresses. Please remember to update! You can find a complete list of addresses here.
  • Docker Build buildkit - Users can now turn on buildkit in the 'Docker Build' action

Improvements

  • It is now possible to ignore hidden files in deployment actions. To do so, use .* to ignore all hidden files or dir/.* to ignore all files hidden in the dir folder
  • When sending a commit status to GitHub we are now providing execution time as well
  • Fixed the pipeline button links. From now on you can use the 'Open in a new tab' option in your browser

Bugfixes

  • [E-mail] Action scope variables were not resolved properly - fixed.
21 January 2020

Buddy v2.2.78 Released (21-01-2020)

Buddy v2.2.78 Released (21-01-2020)

New Features

  • New action: Flutter

Improvements

  • [Buddy Enterprise] Current version requirements changed to 19.03.5 for Docker and 1.24.1 for Docker-compose
  • [AWS CLI, Firebase, GC CLI, Heroku CLI, Netlify, Cloudformation] added the 'Environment' tab. From now on users can install additional tools and packages required for running the action
  • [E-mail] From now on it is possible to set a sender of the e-mails sent via this action
  • [Lighthouse] Added environment variable support for the 'Website URL' field
  • Execution time for the 'Prepare Environment' step is now displayed

Bugfixes

  • There were issues with terminating executions during the 'Prepare Environment' step - fixed
  • In some rare cases - if the pipeline was updated shortly after the execution, the changes were not applied - fixed
PreviousNext