We’re excited to announce that Casandra has just been added to the group of databases that can be used at Buddy. To take advantage of Casandra, just add a new build action or open an existing one, switch to the Services tab and attach Casandra:
- Cassandra service
- We have completed our security & sensitive data audits for GDPR and implemented changes to be ready for the new data protection regulation
- Improved support of pushes and executions. Until now, if the webhook from GitHub/GitLab/Bitbucket contained no information about who made a push, it was assigned to the owner of the integration. From now on, such events will be marked with dedicated avatars
- The mechanism that fetches the repository to the pipeline’s filesystem has been improved. From now on, the fetch will be made with the owner’s permissions no matter who triggered the execution
- Updated Git version on our build servers to 2.17.0
- Added Ruby version 2.5 to Sandboxes
- Ececutions with ‘Clear cache’ applied that were paused and resumed during the process (e.g. by clicking ‘Retry’ or using the ‘Wait for apply’ action) were cleared of cached files once again. Fixed
- The SSH action in line-by-line mode was not showing logs if the action had failed. Fixed! Thanks David for reporting that! :)
A small yet significant change, this week’s update to Run Next Pipeline action will let you optimize your delivery process and release faster in handsome fashion. 😎
From now on, you can force the action to wait until the triggered pipeline has finished, before the original pipeline can proceed with the rest of actions. All you need to do is flip the switch:
- [Pipelines] Run next pipeline action now has an option to wait until the triggered execution has finished before proceeding to the next action
- [Version Control] It is now possible to switch Git integration. When adding a new project from GitHub, Bitbucket or GitLab, the user gives Buddy access over OAuth. However, there was a problem if the project creator lost access to the repository, e.g. was removed from the GitHub organization. From now on, you can change the authorized user in the Project Options. You can also update the source repository which is useful if the original repo or organization name has been changed.
- [Kubernetes] Run K8s job action now supports parallelism
- [Heroku] You can now run Git commands in Heroku CLI action
- [Docker] Run Docker Container action can now be used in pipelines with the branch assignment set to ‘None’
- [Docker] Run Docker Container action now supports Buddy parameters
- By default, the flag ‘Always run queued execution’ is set to
FALSE. This means that all queued executions are skipped and only the newest one is run. This was not working for pipelines with the branch assignment set to ‘None’. Fixed
- AWS S3 deployment validation did not include the target path, which produced ‘Access denied’ in case the user did not have access to the bucket’s root. Fixed. Thanks for the heads up, Jack!
- [YAML] Fixed a bug with incorrect YAML parsing if the trigger time was changed from
ON_EVERY_EXECUTION(default value) to
- [Sandboxes] A month ago we introduced user-friendly URL’s to Sandboxes generated from the branch name and repo slug. However, there was a problem if the subdomain generated was longer than 63 characters. We have solved that by cutting longer subdomains.
In response to more and more questions regarding Buddy badges we’re happy to announce that they’ve finally arrived!
At the beginning of the year, we made a poll where we asked our customers which feature we should add next.
The winner were on-tag releases & PR support. Today we’re delivering the first feature, with the second one following shortly, as the biggest part of the work is already done 😎.
- [Pipelines] Tag push support
- [Pipelines] Buddy will now recommend consecutive actions for your pipeline
- [Pipelines] Easier access to commits and files in the pre-execution review
- [Rollbar] Better support of errors returned by the Rollbar integration
- [CodeDeploy] Better support of errors returned by the AWS CodeDeploy integration
- [Enterprise] The limit for sandboxes has been removed
- Fixed a bug with actions in the ‘On back to success’ section not launching if primary actions contained ‘Wait for Apply’
UPDATE: December 2018
After one year of testing, we have decided to shut down the beta of Sandboxes. Using the feedback that we gathered, we are currently working on a new and improved version of the test environment feature. Make sure to follow us on Twitter for news and updates on the release date.
Sandboxes act as stage servers, allowing you to run your application from a chosen branch with just one click.
Every time you make a push to this branch, the application is rebuilt and run afresh. It’s a great solution for stage branches because the sandbox will always serve the newest code version.
- [Sandboxes] Manual mode
- [Cloudflare invalidation] Sometimes Cloudflare’s API was unreachable so since now the action takes 3 invalidation attempts with a 5-second interval. If all actions still fail, the action ends with ‘Failed’ status
- [Optimization] The application has been optimized for RAM usage in the client’s browser
- [Private Git Hosting] Improved support for errors’ output when fetching repo from private Git hosting. From now on, the error description will allow you to diagnose the issue yourself without the need to contact support
- [SSH] During the connection validation, we now check whether BASH is available on the server (if you chose this shell in the action settings)
- [Buddy Enterprise] Improved settings division and properties description
- [Buddy Enterprise] You can now define the maximum file size that can be committed to the repo (until now it was 100MB)
- [Sandboxes] If you were using your own Docker image with no bash shell, ‘Browse’ in the Sandboxes was throwing an error for binary files
- [Pipelines] Fixed a bug with actions in the ‘On back to normal’ section being executed even when they were disabled
New Features [Limited Beta]
Tag pushes (coming March 27, 2018)
Pull request executions (coming April 2018)
- [Kubernetes] Overwrite/Cascade and Validate flags are now set to true by default in the Apply Deployment action
- Opening a stacked view now always display the name of the parent project on the top navi-bar (e.g. when opening an element from the global Activity stream)
- AWS ElasticBeanstalk and CodeDeploy actions now support ENV VAR in the source path
- Improved support for
.gitignorein Deployment from Heroku/Azure and Git Push actions. All of them now deploy artifacts and code processed in previous actions by default
- [Enterprise] You can now set maximum size for files commited to the repo
- [Enterprise] Added a validator for GitLab integration that will check for the protocol in the URL to the GitLab instance
- Fixed a bug witch cloning a pipeline with two Wait for Apply actions that was causing the app to crash
- Generating pipeline statistics in large projects no longer causes timeouts
- Opening details for a commit that was previously removed from the repo now produces an error