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 customioze your pipelines even more: the possibility to parameterize your execution.

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.

Buddy v2.0.9 Released (13-02-2018)

New Features

Improvements

  • Mount pipeline filesystem – you can now decide if you want to attach a filesystem to builds and/or the Docker run action, or run them without it
  • Methods used to display commit data have been optimized, which greatly improved the loading times
  • CLI in the Amazon CLI action has been upgraded to v1.14.35
  • New division of build actions

Bugfixes

  • Fixed bug with adding Sentry On-Premises: a wrong HEADER was being sent which made it impossible to add the integration. Thanks Jake for reporting that!
  • [Sandboxes] Fixed bug with Redis data getting lost between each sandbox start-up even if the Persistent Storage option was checked

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:

Get started now

14 days of unlimited trial. No credit card required.