Buddy v1.5.55 Released

New features

  • Trigger conditions in actions
  • New integration: DigitalOcean Spaces
  • New integration: Vultr
  • New integration: Honeybadger

Improvements

  • The filesystem type in the Docker Build action has been changed from AUFS to overlay2. This has solved the problems reported by some of our clients and speeded up the action up to 3 times
  • You can now precisely schedule build execution in recurrent pipelines settings
  • Buddy parameters are now supported in the working directory of the SSH action and the target branch field of the Git push action
  • Removing pipelines with monitoring actions could be very time-consuming due to the time needed for executions removal. We have fixed the indexing and reduced it to a couple of milliseconds at most
  • The timeout for GitLab connections has been prolonged to 5 minutes (the response time from GitLab can be very long which sometimes made the integration to crash)
  • It is now possible to look up pipelines on the Table view

Bugfixes

  • Fixed namespace support in methods checking the job status in the Run Job (K8s & GKE)
  • Projects to which you don’t have permissions in the Deploy to Google App Engine action will no longer be listed

Buddy v1.5.54 Released

New features

  • New integration: Rollbar
  • New integration: Datadog
  • You can now use SSH keys defined in the environment variables in actions using SSH authorization (SFTP, SSH, Rsync, Git push, etc.)
  • New version of Sandboxes released for private beta testers

Improvements

  • Rsync deployments now support Buddy keys
  • Cloning a pipeline will now clone static files and visibility settings, too
  • It is now possible to set up the mount path for the pipeline filesystem in build actions with YAML/API

Bugfixes

  • Fixed browsing in the Rsync action (didn’t work as Rsync was authorized with an SSH key)
  • Fixed bug with testing and sending Slack attachments

[IMPORTANT] Weekly maintenance rescheduling

This week the service maintenance will be performed exceptionally on Thursday, November 23, at 06:00am UTC (01:00am EST).

This is because we need to release a new infrastructure for the upcoming Sandboxes feature. The update will last about 1 hour and only concerns Buddy Cloud—the release time for Buddy Enterprise is soon TBA.

New feature: Sentry integration

We’re happy to announce that Buddy officially supports Sentry bug tracking and reports!

WARNING: With the release of Buddy v2.0.2, the integration is available for both cloud and on-premises installations of Sentry.

Sentry helps developers identify and debug errors before they make it to production. With a detailed insight into the error you can quickly decide whether to apply a hotfix or roll back changes. The tool lets you apply filters to stack traces to reduce noise and reproduce errors without user feedback with each bug’s history of events and users actions—a perfect complement to Buddy’s delivery pipelines.

Feature update: Deploy builds to Heroku

In response to numerous requests from the community, we’re happy to announce that our Heroku action now supports build deployments.

Until now, it was only possible to deploy raw files from the repository. With the last release you can use Buddy to build your application first and deploy it to Heroku in its final form with artifacts and dependencies. This solution brings a series of benefits:

AWS CodeDeploy – Deployment status update

AWS CodeDeploy enables developers to automate code deployments to Amazon EC2 instances and on-premises servers.

It scales with the cloud infrastructure, allowing to deploy the same application revision to multiple nodes at once across different environments + tracks application health according to configurable rules.

Buddy v1.5.53 Released

New features

  • Buddy key regeneration
  • AWS CodeDeploy: added ‘Wait until deployment has finished’ option
  • Heroku: you can now deploy files processed in build actions, for example you can build assets with Gulp or Grunt, and push the source code to Heroku

Improvements

  • Better error support in AWS CodeDeploy & Elastic Beanstalk when authentication data does not allow to add an S3 bucket (deployment to EB requires permissions to S3 buckets). Click here for the full list of AWS policies
  • Fixed error support when too little RAM is assigned to build actions. At the moment, all build actions are executed in Docker containers with 2GB of RAM. In a couple of weeks you will be able to buy custom plans with more RAM and vCPU’s
  • It is now possible to define trigger conditions with API and YAML
  • We’ve changed the way changes are fetched to the pipeline’s filesystem, which solved lots of problems with .git metadata
  • Short hash has been added to the execution view (until now you had to open an extra link to copy the revision of the execution)

Bugfixes

  • Fixed bug with synchronizing private repositories in case authorization data used for checkout contained a question mark ?
  • Fixed bug with the ‘Wait for apply’ action not working correctly for free accounts (caused by the global queue)
  • Fixed bug with pipelines not marking actions as disabled when cloning
  • Fixed bug with browsing paths in the ‘Deploy to AWS S3’ action (paths different than root were not being listed properly). Shout out to Roland for pointing that out!

Updates

  • Docker upgraded to v17.09

Buddy v1.5.51 Released

Improvements

  • From now on environment variables in pipelines can be managed by all users with the ‘Pipeline: Manage’ level of permissions. You still need to be an admin to manage the project and workspace tiers of the variables, though
  • There’s no need to clear the cache upon changing the clone depth in the pipeline settings anymore
  • Upload from scratch is now available in AWS Elastic Beanstalk deployments
  • Docker images with self-signed certificates can now be pushed to the registry
  • Transactions and invoices have been separated in the Billing tab

Bugfixes

  • Fixed bug with wildcard pipelines in recurrent mode not working correctly if the option ‘execute only if there were changes in the branch since the last execution’ was set

Better support for multiple integrations

Buddy is a delivery automation tool that heavily relies on integrations with other services like AWS or Google Cloud.

Until now, the integration was performed at the moment an action has been added for the first time. If you wanted to add more integrations to a service, you had to do it from the Integrations tab in My-ID settings.

Get started now

14 days of unlimited trial. No credit card required.