23 June 2020

Buddy v2.3.38 Released (23-06-2020)

Buddy v2.3.38 Released (23-06-2020)

Improvements

Bugfixes

  • Fixed a bug with build-args values not being properly escaped in the Docker build action
  • Fixed a bug with the validation mechanism not passing properly added redirectUrl's when adding an OAuth application
  • [FTP / SFTP] Fixed a bug with Test action and Browse remote path not working properly if the path started with ~
  • [REST API] Fixed a bug with the clear pipeline cache method not working if the project had YAML configuration enabled
19 June 2020

New action: Shopify Theme Kit CLI

New action: Shopify Theme Kit CLI
Shopify is a cloud-based commercial platform allowing you to easily build online stores. For a long time Buddy has enforced web developers in their job with bulding, testing, and deploying themes to Shopify stores. This week we deliver a new functionality that expands the scope of automation even further: the Shopify Theme Kit CLI.
18 June 2020

Orchestrate containers on DigitalOcean Kubernetes

Orchestrate containers on DigitalOcean Kubernetes
With this week's release, we expand the roster of supported clusters with DigitalOcean Kubernetes. We love the simplistic approach of DigitalOcean towards cloud computing as it perfectly aligns with our conception of DevOps and CI/CD. The more happy we are to deliver the official DigitalOcean integration to the set of actions that will let you easily update and manage your apps on Kubernetes clusters.
17 June 2020

New action: SSL verify

New action: SSL verify
SSL certificates let you provide authentication to your website and secure the sensitive data of its visitors. Today we are expanding our monitoring actions roster with the SSL verify action that will let you control if the SSL certificate on your website is valid.
16 June 2020

Buddy v2.3.37 Released (16-06-2020)

Buddy v2.3.37 Released (16-06-2020)

New Features

Improvements

  • Deployment actions can now be configured not to delete the files removed in the changeset from the remote server (applies to actions based on changeset only)
  • It is now possible to tag files deployed with the AWS S3 action
  • It is now possible to regenerate Role external ID in the Amazon integration

Bugfixes

  • Fixed a bug with occassional error message when adding a new branch in Buddy's GUI
  • Sometimes adding an integrated repository resulted in an error although the synchronization passed through successfully. Fixed
4 June 2020

Introducing: Azure CLI

Introducing: Azure CLI

Although not as popular as AWS or gcloud, Microsoft Azure has already created a resiliant community on our platform. Right now, you can use Buddy to easily automate deployment to the Azure App Service. In two weeks time, however, we are going to deliver support for Azure Storage, followed by the much requested integration with Microsoft Teams (currently in production).

This week we released yet another new action called Azure CLI. The action acts as an API client, allowing you to run basically any type of operation in the Microsoft's cloud: from creating a virtual machine, to managing App Service instances, to orchestrating containers on an AKS cluster.

2 June 2020

Buddy v2.3.34 Released (02-06-2020)

Buddy v2.3.34 Released (02-06-2020)

New Features

  • New action: Azure CLI

Improvements

  • [REST API] You can now clear pipeline cache using the API
  • [Docker] Google Container Registry (GCR) now supports the gcr.io region

Bugfixes

  • Fixed a bug with the project deletion message being displayed wrongly if the project name contained multiple consecutive spaces in the name
26 May 2020

Buddy v2.3.33 Released (26-05-2020)

Buddy v2.3.33 Released (26-05-2020)

Improvements

  • [Helm] If the cluster is set to EKS, the repository is set to S3, and both are in different regions, the action assigns the S3 region to the $AWS_DEFAULT_REGION variable
  • If a pipeline is not assigned to any branch (ref_type: "NONE") and contains a Run next pipeline action triggering a pipeline in wildcard mode, the action will be failing with a message that such configuration is not possible

Bugfixes

  • [Buddy Enterprise] Fixed a bug with file variables not being loaded to build containers
  • [YAML] If a pipeline was in progress, the execution to follow triggered by git push were made for the HEAD revision instead of the corresponding revision. Fixed
  • If an email address was entered as a login in the adress used for git clone/git fetch/git push to a repository hosted on Buddy, the entries in the access logs were marked as failed despite proper authorization. Fixed
22 May 2020

Feature spotlight: SSH Keys

Feature spotlight: SSH Keys

SSH keys remain one of the most secure authorization methods. The keys are generated in pairs. The first one is the public key, which is installed on the server. The second one is the private key, which is used to authenticate on that server. SSH keys are generated using cryptographic algorithms such as RSA, DSA or ECDSA, which makes breaking them with brute-force attacks practically impossible.

SSH keys are most commonly used for authentication on SSH servers to excecute remote commands or to upload files. They are also used for authorization when connecting to Git repositories (git clone, git pull, git push).

The high level of security they provide makes them also the most popular method of authorization in CI/CD processes. They are used, among others, for:

  • Authorization in Git repositories
  • Authorization during dependency download
  • Authorization while downloading submodules
  • Authorization during remote command execution on the server (DB migration scripts, application restart, etc.)
  • Authorization during file upload to the server (Rsync, SFTP, SCP)
19 May 2020

Buddy v2.3.32 Released (19-05-2020)

Buddy v2.3.32 Released (19-05-2020)

Improvements

  • Download actions now support ignore paths
  • Docker layer cache management has been optimized for more efficient storage usage

Bugfixes

  • Fixed a bug with incorrect mapping the push author in custom repositories
  • Fixed a bug with the Slack action failing whenever the message was longer than 3000 characters. Since this limitation comes from Slack and we cannot increase the limit on our end, all messages are now limited to 3000 characters