17 May 2017

New feature: Google CDN

New feature: Google CDN

Google developers: you can clear your CDN cache on every deployment with the new purge action

Google CDN is one of the Content Delivery Networks. That means, when a user opens the website, the files are served from the closest server location which shortens the time required to open your website.

10 May 2017

New feature: Elastic Beanstalk Monitoring

New feature: Elastic Beanstalk Monitoring

Pipelines in Buddy are flexible enough to reproduce almost every type of workflow. Here are the three most popular use cases:

  1. Delivery – used to upload repository files or compiled app to the server on every push to branch, recurrently at a given time, or manually on click.
  2. Continuous Integration Server – used to run unit and integration tests on every push to repository and send notifications if the tests have failed
  3. Monitoring – used to check the status of website or server on given intervals and send a message in case it goes down.

In this article we’ll cover practical use of the new EB monitoring action in the context of existing delivery pipelines.

10 May 2017

New feature: AWS CLI

New feature: AWS CLI

Every developer in the world knows exactly what AWS is. So does Buddy: it even has a separate section for Amazon services only. You can, for instance, upload a new version of the application to Elastic Beanstalk, deploy files to S3 or launch a Lambda function.

3 May 2017

Update to Atomic deployments

Update to Atomic deployments

Atomic deployments are the first in the series of pipeline templates that we introduced to Buddy.

In short, they allow you to update your website with zero downtime by uploading the files a cache directory on the server and switching the symlink of the web server to the new version when everything’s finished.

Recently we’ve modified the template by adding a feature that lets you define how many website versions you want to keep on the server.

27 April 2017

Introducing: Private Git repositories

Introducing: Private Git repositories

We’re excited to announce that private repositories are now supported by BuddyWorks!

This means you can hook up Buddy with repositories on your private Git server, as well any other external Git provider, including:

  • Assembla
  • CloudForge
  • Codebase
  • Deveo
  • RhodeCode
  • Springloops
  • Visual Studio Team Services

All you need to do is provide configuration details of your repo + set up a web hook in your version control that will automatically refresh the list of commits in Buddy and trigger the deployments:

Private repo configuration screen
Private repo configuration screen

So, if you guys know of any developer who couldn’t use BuddyWorks because it didn’t support their Git provider, do not hesitate and spread the good news! 🙌

26 April 2017

Introducing: Rsync deployments

Introducing: Rsync deployments

The most popular pipeline feature in Buddy is code delivery. You can use one of the many integrations to deploy your code – such as Elastic Beanstalk, Amazon S3, Rackspace, Google Cloud Storage or Microsoft Azure – or stick to the standard SFTP/SCP protocols, or even the good ol’ FTP.

Deployment tools such as Capistrano may be used as well, with Rsync joining the party in the latest release.

Rsync is a great tool which allows you to sync files between different locations. It checks the files and uploads only those that were changed. Until now you could only use Rsync by defining custom upload scripts in build actions at the end of the actual build commands.

In response to high popularity of this action, we’ve decided to add a dedicated action for Rsync. All you need to do is provide the server details and the path where the files will be uploaded, and Buddy will handle the rest for you.

Rsync action details
Rsync action details

Additional options

By default, the Rsync action has these options enabled:

  • Compress file data during the transfer: Files are compressed on the upload, which increases the upload speed
  • Archive mode: this feature allows you to move symlinks (without hardlinks), permissions and groups, as well as times of file and owner modification
  • Delete extraneous files: when a file is deleted in the pipeline filesystem, it will also be deleted on the host.

If you’d like to learn more about Rsync and introduce it to your workflow, just let us know at the chat at the bottom right corner, or drop a word to support@buddy.works.