15 January 2019

Buddy v2.1.48 Released (15-01-2019)

Buddy v2.1.48 Released (15-01-2019)

New features

  • New integration: Deployment to UpCloud
  • New SSH implementation – the new library allows for new types of keys in Git authorization and SSH/SFTP actions
  • Variables in REST API – from now on you can manage your Workspace/Project/Pipeline variables via the API

Improvements

  • New Default Variable: $BUDDY_EXECUTION_CHANGELOG
  • New Default Variable: $BUDDY_EXECUTION_PULL_REQUEST_NO. Contrary to $BUDDY_EXECUTION_PULL_REQUEST_ID which produced the PR name as pull/[number], the new variable only contains the number
  • [AWS] By default, the AWS S3 action sets the MIME type of uploaded objects. It is now possible to disable this feature
  • [SSH] When executing commands on a server with the SSH action in the script mode, Base64 is required on the server. Buddy will now validate it before the execution
  • [UI/UX] Improved forms for adding/editing action — fixed issues with browser autofill and remembering password modals

Bugfixes

  • [Docker] Adding two Docker build actions and setting them in parallel was resulting in a failed execution. Fixed
  • [Docker] Fixed a bug with the flag ‘Allow connection to insecure registry’ wasn’t working properly for all URLs in the ‘Push Docker image’ action
  • [Trigger conditions] Fixed a bug with ENV VAR trigger conditions not working in pipelines whose branch assignment is set to NONE
  • [Docker] Using ENV VARs in the source path in the ‘Push Docker Image’ action was casuing with incorrect path. Fixed
  • [Buddy Enterprise] Improved Azure application and ontegration support for all K8s actions