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


26 May 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

About the Author

Customer Success Manager

A story-teller and conversation-lover, Alexander decided to invest his skills to help his friends at Buddy transform the cold language of patch notes into exciting narratives. Also: an avid gamer, hip-hop DJ, Liverpool FC fan, absentminded husband, and the father of two.

Buddy Makes Developers Happier

You use lots of tools to get web & app development done. Buddy creates more time in your day by helping you automate those tools.

Continue reading

This post was originally published on this site