Blog

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

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.

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)

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

Improvements

• Pass Arguments now supports variables in the path to the options file
• Elastic Beanstalk & EB Monitoring now display the environment ID on the Environment list

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

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

New Features

• New action: Link Validator

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

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

• Improved support for the MySQL service for v8.x.x
• The Visual Tests action can now be properly cloned