12 May 2020

Buddy v2.3.31 Released (12-05-2020)

Buddy v2.3.31 Released (12-05-2020)

Improvements

Bugfixes

  • Browsing files in a revision which didn't belong to any branch caused errors. Fixed
  • Fixed an occassional issue with updating environment variables not working properly
  • If a pipeline executed on tag push triggered another pipeline in wildcard mode using the Run next pipeline action, the environment preparation step in the second pipeline crashed. Fixed
5 May 2020

Buddy v2.3.30 Released (05-05-2020)

Buddy v2.3.30 Released (05-05-2020)

Improvements

  • SSH keys now display the public key and fingerprint
  • It is now possible to select the key used to fetch submodules
  • You can now select the workspace key as the authorization method in SSH, SFTP, and RSYNC actions
  • Added ENV VARs to launched containers in which key = name of the SSH key, and value = path to the file with the key's content
  • [Android] Added custom tracks support to Publish APK and Publish Bundle actions

Bugfixes

  • Fixed a bug with returning an incorrect error when browsing a remote server if the provided path was wrong
  • Fixed a bug with submodules being fetched to the filesystem even though the fetch option was turned off
  • Fixed a bug with project listing if one of the selected integrations was broken when adding an integrated project
30 April 2020

New action: Link validator

New action: Link validator
500 and 404 errors are a bane of every successful SEO. In theory, Google does not lower the grade of your page just because it contains a couple of 404 errors. In practice, however, such links are unable to contribute to your "PageRank" and significantly lower your search traffic and link power – not mention that your readers are not able to access the valuable content that such link may hide.
28 April 2020

Buddy v2.3.29 Released (28-04-2020)

Buddy v2.3.29 Released (28-04-2020)

New Features

Improvements

  • It is now possible to trigger a wildcard pipeline with any revision. Previously, it was only possible by selecting the matching branch, tag or pull request

Bugfixes

  • [Notifications] Removing file attachments did not work properly when trying to remove all attachments
  • If a build action used services launched from private images hosted on Docker Hub or a private registry, updating the password to that registry did not work properly. Fixed
  • Fixed a bug with Kubernetes actions not accepting certificates provided with environment variables
23 April 2020

New feature: File variables

New feature: File variables
Handling and managing sensitive data is extremely important in the CI/CD process. This type of data shouldn't be kept in the repository to avoid unnecessary risk. You can, however, store it in Buddy in the form of variables, en elegant an practical solution for every developer.
21 April 2020

Buddy v2.3.28 Released (21-04-2020)

Buddy v2.3.28 Released (21-04-2020)

New Features

  • New type of environment variables: File

Improvements

  • GitHub, Bitbucket and GitLab projects now load faster on the Projects tab
  • You can now view the cache size for each pipeline in the new Cache tab in workspace preferences
  • You can now select which actions you wish to copy when cloning a pipeline
  • It is now possible to ignore errors while pulling public images in build actions – in case of connection problems, Buddy will use a cached image instead
  • Download actions now support trigger conditions and list files when browsing the source path
  • It is now possible to set GitLab EE and GitHub EE nickname in the user profile
  • It is now possible to switch between BASH and SH shell in the following actions: AWS CLI, Kubectl, Helm CLI, and Google Cloud CLI
  • Improved support for excluded paths in the following actions: ZIP, AWS Elastic Beanstalk, AWS CodeDeploy, and AWS Lambda Deploy
  • [AWS Elastic Beanstalk Monitoring] Added ENV VAR support for the Environment field in YAML and REST API

Bugfixes

7 April 2020

Buddy v2.3.26 Released (07-04-2020)

Buddy v2.3.26 Released (07-04-2020)

New Features

  • Webhook logging – the webhooks that you receive from your Git provider are now logged in the Repository tab of the project options. This option is especially useful when diagnosing why your pipelines are not triggering despite pushes to the selected provider.

Improvements

  • [Upload to SFTP] The transfer speed of large files to an SFTP is now 10 to 20 times faster (!)
  • [Security] It is now required to confirm your email before accessing the workspace and pushing code to Buddy Git hosting
  • The invoker for executions triggered with pull requests in automatic mode is now being set properly
  • When accessing Buddy via GitHub or Bitbucket, your username will now be the same as in your Git provider account
  • Webhook response logging - until now, only the sent payload was saved. From now on, Buddy also logs body and headers of the provided response
3 April 2020

From Beanstalk to Buddy in one weekend

From Beanstalk to Buddy in one weekend
Kyle Carlson is the lead developer at Lifted Logic, a web design, SEO & web development agency in Kansas City, USA. For a long time he and his team was using Beanstalk for code hosting and deployments. However, with new clients flocking in on the regular basis, the company ultimately hit the tool's limit on the number of repositories. And, in the industry where projects need regular updates, this became more than a nuisance.