Buddy v2.0.8 Released (06-02-2018)

New Features

  • Database seeding in Sandboxes. It is now possible to seed databases by uploading an SQL dump to the repo
  • Services configuration. You can now define the hostname, username and password in the database services in pipelines and sandboxes

Improvements

  • Access to Forum & Documentation is now easier thanks to the dedicated Help (lifebuoy) icon on the top navi-bar. You can also use it to send an instant message to our team
  • You can now define the application in the Heroku CLI. This way, you won’t have to do it again for every command with a parameter
  • It is now possible to resend email confirmation messages. Until now, such message was only sent once (upon configuring the new address)
  • The method used to fetch executions has been optimized. In some cases the time required fetch an execution could be 20 times faster (e.g. long logs with lots of encrypted ENV VARs)

Bugfixes

  • In the ‘Run next pipeline’ action, the comment from the execution that was triggering the second pipeline was not being transferred. Fixed

Buddy v2.0.7 Released (30-01-2018)

New Features

  • New action: ESLint

Improvements

  • [Sandboxes] Cloning a sandbox will also clone database settings
  • [Sandboxes] You can now run post-build commands that will be executed once the sandbox has launched, e.g. database operations
  • In the Git push action you can now use options ‘Don’t deploy changes made by previous actions’ and ‘Use .gitignore from repo’
  • Improved support for configuration errors in the Sentry action
  • Improved long path support on diff and commit views
  • [Standalone] Backup will also include static files uploaded to the pipeline filesystems

Bugfixes

  • Running all pipelines at once was ending with an error if one of the pipelines had a wildcard for a trigger mode
  • Zip action: if the name of the target file is not parameterized (i.e. it’s the same for every execution) the old archive is now removed before the execution, so that the new one is not updated but created from scratch
  • The changes in the Zip action also affect deployments to ElasticBeanstalk/CodeDeploy, meaning the removed files will no longer be present in the new version

New action: ESLint

ESLint is an open source tool for analyzing and fixing code violations in JavaScript according to the chosen code style: Airbnb, Facebook, Google and many others.

Usually, ESLint is run with Gulp or Node tasks before the deployment. In this case, you just need to it to your build action. We have added the action specifically for users who like to keep things as simple as possible. The tool is best used as the final touch before the deployment making your code more consistent:

Buddy v2.0.4 Released (23-01-2018)

Improvements

  • Improved navigation (breadcrumb) in Source/Filesystem/Sandbox Browse
  • Increased message content size in the Email notification action from 5k to 20k characters
  • From now on folders containing artifacts in the pipeline filesystem are accordingly marked, too
  • [Enterprise] You can now bind the application to a specific IP if your server has more than one external IP address
  • [Enterprise] Static files in pipelines are now backed up in a dedicated location

Bugfixes

  • The ‘Download code’ option in the Browse tab was downloading code for the default branch, instead of the currently browsed revision. Fixed

Updates

  • Amazon SDK upgraded to v1.11.263
  • Jackson library upgraded to v2.9.3
  • Rackspace library upgraded to 2.0.3
  • Kubernetes client library upgraded to v3.1.8

Help us decide!

Get involved in our development process by helping us decide which feature we should deliver next.

Parallel Commands

Split commands in sets and run them simultaneously to speed up the performance of your pipelines.

WARNING: Vote for Parallelism


Run Pipelines on Tag Push or Pull Request

Run pipelines on branch or tag push, or on pull request in addition to the existing trigger modes (on push, on click, recurrently).

WARNING: Vote for New Triggers

New action: Kubernetes CLI [kubectl]

We’re excited to announce it is now possible to run commands with kubectl in your K8s clusters.

Our Kubernetes integration was met with massive interest from Docker enthusiasts. However, no two workflows are the same and it soon appeared the existing set of K8s actions was insufficient for some developers who demanded more power and flexibility.

Buddy v2.0.3 Released (16-01-2018)

New Features

  • New action: Kubernetes CLI [kubectl]

Improvements

  • You can now apply the ‘Ignore errors’ flag in the SSH action through the API and YAML. The flag lets your mark the action as successful even if some errors occured
  • Improved .gitignore in the Git Push action: you can now exclude files from the origin repository (GitHub, Bitbucket, GitLab, Buddy, etc.)
  • It is now possible to upload files to FTPS servers with SessionReuseRequiredTransfer flag applied

Bugfixes

  • Fixed the problem with fetching submodules to the pipeline’s filesystem

New integration: Loggly

We’re excited to announce that yet another awesome service is joining the roster of Buddy’s integrations.

Loggly analyzes log files from all your distributed systems allowing you to detect anomalies and take action if necessary. Build around interactive dashboards, Loggly lets you create alerts based on specific search patterns, thresholds and metrics, so you can quickly inform your team mates before a suspicious event turns into a problem.

New action: PHP_CodeSniffer

PHP_CodeSniffer is a nifty little tool that lets you detect and fix code violations in PHP, JS and CSS files so that you can upkeep the high quality of your code.

The tool is best used as the final touch before the deployment:

Get started now

14 days of unlimited trial. No credit card required.