Buddy v2.0.15 Released (06-03-2018)

Improvements

  • The Eslint action now supports custom configs
  • You can now use \ (backslash) to enter multi-line commands in the Environment Customization tab
  • The comment field in the execution run has been brought to front from ‘More options’
  • [Sandboxes] If the indicated SQL dump file is no longer in the repository, Buddy will show you a warning in the logs
  • [Sandboxes] Support for Webpack v4.0.0

Fixes

  • [Sandboxes] Removing a branch now also removes the assigned sandbox
  • [Sandboxes] Fixed WP Theme & Plug-ins stack
  • Sometimes deleting a pipeline would produce errors in other browser tabs where the pipeline was active

Support for deleted files in filesystem deployments

As you know, the deploy mechanism in Buddy is based on changesets.

This means that only new and changed files are deployed to the server. Plus, if a file is deleted from the repository, it will also be deleted from the remote. Unfortunately, the last part wasn’t true for deployments from the filesystem, which was not “aware” of deleted files. Until today.

BASH support for Docker-based actions

Docker containers are the natural environment to many different Buddy actions.

No matter if you run commands in the Local Shell, build a Node application, test a PHP website, or compile Java – they all use Docker containers as their running environment.

Buddy v2.0.13 Released (27-02-2018)

New Features

Improvements

  • Atomic deployment templates have been updated, covering new additions to the SSH action
  • [Buddy Enterprise] It’s now possible to manually set the number of available pipeline concurrent executions
  • [Run K8s Job] New option: Don’t wait for the job to finish before proceeding
  • [Run K8s Pod] New option: Don’t wait for the operation to finish before proceeding

    Fixes

  • Frequent deletion of branches was causing glitches to buddy.yml
  • If there was no info who pushed the branch in the web hook from GitHub, the branch did not show up on the list in Buddy
  • [YAML] run_as_script in the SSH action
  • Cloning a sandbox didn’t set the proper name for the new one (Thanks Cameron!)

Introducing: Parameterized Executions

When the idea of Buddy was shaping, our desire was to make a Continuous Delivery tool that will be easy to set up, but also flexible.

Today we’re adding another brick that will let you customize your pipelines even more: the possibility to parameterize your execution.

Action upgrade: SSH v2.0

The SSH action is one of the most popular actions used in Buddy’s pipelines. In Today’s release the SSH action gets some love. Thanks to your feedback, we’ve introduced some new features.

Live logs

{% vimeo 256952935 %}

Buddy v2.0.10 Released (20-02-2018)

New Features

Improvements

  • Action upgrade: SSH v2.0 – New run mode (run as a shell script) & live logs
  • Upon triggering an execution without a cache, the build command in the Build Docker Image action is run with --no-cache parameter by default
  • ‘Packages and Setup Commands’ have been renamed to ‘Environment Customization’. We have changed that because many users were performing operations reserved for the main commands, such as downloading dependencies (composer install / npm install)
  • [Sandboxes] User-friendly domains: the URL to the sandbox is now generated using the name of the project and branch

Bugfixes

  • Fixed bug with deployments with a large number of files finishing as failed

Introducing: Run Docker image

Docker is encoded in Buddy’s DNA. Most of pipeline actions, like builds or shell commands, are performed in Docker containers. With Buddy you can build Docker images and push them to a registry. You can also integrate with Kubernetes and Google to manage your Docker clusters.

In response to demand from other Docker enthusiasts, we have added an option to run Docker containers with a dedicated action.

Get started now

14 days of unlimited trial. No credit card required.