New feature: Cloudflare integration

In response to popular demand we have added Cloudflare CDN support to Buddy.

Cloudflare is one of the most popular Content Delivery Networks in the world, along with AWS Cloudfront. In short, it’s a global cache: when a user opens the website, the files are served from the closest server location which drastically speeds up the loading time.

Buddy v1.4.45 Released

New features

Improvements

  • Docker has been upgraded to v17.03.0-ce
  • We have added a new action to the DevOps section: Terminal, a Docker container with pre-installed Ubuntu 16.04 that you can use to run scripts on our servers. The action was available from the beginning, but we decided to give it more exposure due to popularity
  • From now on you can send execution logs in notification action: ${execution.action_executions[index].log}
  • Modulus deployment client has been upgraded to the newest version
  • Files in the Docker build action are now cached per action, not per pipeline. This way the action no longer invalidates caches of other actions

Bug fixes

  • Clients who had more than one Slack integration added were not able to test the Slack notification action because of the ‘channel not found’ error. Fixed
  • Fixed bug with environment variables in the Web Monitoring action not being tested upon adding the action
  • Refreshing the repository now properly clears the cache
  • If the pipeline filesystem contained absolute symbolic links, the changeset calculation method didn’t work, which caused the deployment to crash. Fixed

Run apps directly from your Git repository with Buddy!

We’re happy to announce that Sandboxes are coming to Buddy! This means you will be able streamline your process by launching your apps directly from your Git repository.

Yes, this is the BIG feature that we’ve been teasing you with in the past couple of weeks. The main part of development has been finished and we are currently testing it inside-out. By mid-April we should be ready with beta for you to check out. Stay tuned for more information, and in the meantime check out how it works in our super-exclusive video below:

{% vimeo 210749803 %}

Version Control: Feature overview

In addition to GitHub, Bitbucket and GitLab support, Buddy offers a fully-featured Git hosting for private repositories, both in cloud and self-hosted version. This option is useful for people who like to keep everything in one place, prefer a clean GUI over cluttered interface, or cannot use any of the aforementioned Git providers for whatever reason.

Buddy v1.4.44 Released

New features

Improvements

  • Changed condition for skipping recurrent pipelines. From now on, if there’s more than one execution queued in the pipeline, only the first newest will be executed.

Bug fixes

  • [REST API] Fixed method fetching project list. The bug has officially claimed the 1st place for the most ‘WTF?’ bug in the history of Buddy: if a project was starting with the ‘API’ word, it was not returned (?). Big shout out to Marco for pointing that out!

Buddy v1.4.43 Released

New features

Improvements

  • You can now recreate GitHub, Bitbucket and GitLab integrations in /my-id settings if you have problems resynchronizing your repositories
  • Action and execution views have a new, more compact design

Bug fixes

  • Fixed default commands for the Jekyll action
  • Fixed bug with automatic pipelines not triggering if there was another pipeline with branch assignment set to ‘None’

Buddy v1.4.41 Released

New features

  • The BIG feature that we announced last week has just left the testing phase and was merged to the DEV branch. If all goes well, it should be live in about one month

Improvements

  • It is now possible to resynchronize the repository with your provider. Buddy uses webhooks to fetch information about changes in GitHub, Bitbucket and GitLab repositories. Sometimes, for reasons independent from us, the web hooks did not reach our service and the changes were not reflected in Buddy. Clicking Resynchronize Repo in the Code tab will fetch the latest version of the repository and trigger dependent pipelines
  • When adding a new deployment action to a pipeline which has already been executed you will be asked if you want to deploy the files from scratch. This way there won’t be any problems with badly calculated changesets on the first execution

Bug fixes

  • Some time ago we made some improvements to action validators and accidentally entered a bad regex which prevented adding actions containing an underscore. Fixed
  • There was a bug in one of the external libraries used to send the status of execution to GitHub which caused recurrent pipelines to crash. We have reported and fixed that on the very same day [applause]
  • If there are more than 100 files in the changeset the diffs for them are not displayed by default and you need to expand them manually. Sometimes there was a problem with that. Fixed
  • [Buddy GO] Fixed bug with the wrong number of concurrent executions available for Enterprise licenses. If you’re a Premium user and still have this problem, please refresh your license at $URL_TO_STANDALONE/payments/license

Get started now

14 days of unlimited trial. No credit card required.