Blog

13 June 2017

Buddy v1.5.24 Released

New features

Improvements

  • Don’t skip flag. A single pipeline cannot be undergoing more than one execution at a given time. In other words, if the execution is in progress and another user runs the pipeline, the second execution will be queued and won’t start until the first one is over. However, if there are more executions in the line (for example 5), Buddy will only run the newest execution (5) and skip the rest (2-4). From now on you can check Don’t skip in the pipeline and Buddy will run all executions one by one. This feature is useful if you want to check every single commit for errors
  • You can now parameterize the URL address in the Web Monitoring action with env variables and Buddy parameters
  • From now on the errors thrown on the server side by HTTP requests will be covered in a detailed stacktrace in the action logs
  • You can now temporarily disable specific actions in the YAML file by adding "disable: true" to the action properties

Bug fixes

  • When two or more pipelines were triggered and queued, the pipeline that was triggered last was executed as the first in line. From now on the pipelines will be executed in the natural order they were run.
  • One of our clients (cheers Mike!) reported a problem with fetching feeds on the Activity stream. We’ve changed some indexes in Mongo DB and fixed it
  • Fixed bug with running pipelines with HEAD revision set fetching the revision from the default branch instead of the branch set in the pipeline
7 June 2017

Feature roadmap for June 2017

UPDATE: December 2018

After one year of testing, we have decided to shut down the beta of Sandboxes. Using the feedback that we gathered, we are currently working on a new and improved version of the test environment feature. Make sure to follow us on Twitter for news and updates on the release date.

It’s been a busy couple of months for the team at Buddy.

As you can learn from our weekly newsletter, we’re doing our best to drop new features regularly, their priority always reflecting current demand from the community. Here’s a few words on what we’re working on at the moment, and what we’re cooking for the months to come.

6 June 2017

Buddy v1.5.21 Released

New features

  • New integration: Kubernetes. You can now apply K8s deployment configs, set images in K8s deployment, and run K8s jobs.

Improvements

  • A followup to using Slack as a deploy bot, it is now possible to run deployments with a short hash code
  • You can now use the list of commits and the list of added/modified files in the Buddy parameters. The full list of parameters is available here

Bug fixes

  • For some users the DigitalOcean integration was not listing droplets when adding a new deployment action. This was caused by the token not refreshing correctly. Fixed
  • Fixed bug with Google Cloud Storage deployment not working properly if the source path indicated a single file instead of a folder
  • Fixed bug with listing projects in Google Cloud Engine. Just like with DigitalOcean, this was caused by the token not refreshing correctly
  • [Buddy Enterprise] Fixed bug with wrong allocation of RAM to Docker containers, which in some cases caused the installation process to fail.
1 June 2017

Webpack vs Gulp

With the rising popularity of Webpack more and more people start comparing it with Gulp.

Fierce discussions populate comment sections of web development websites about which one is better. In this article we’ll show you what Webpack is, how it differs from Gulp, and – most importantly – which one you should use.

30 May 2017

Buddy v1.5.19 Released

Improvements

  • Environment variables are now supported in private_key and passphrase inputs of the Git Push action
  • Due to different server configurations of our users we have decided to remove remote directory validation on the server—there will be no more problems with adding SSH actions. NOTE: if the specified directory does not exist on the server, the first execution will end as failed
  • You can now use the filesystem in pipelines with branch assignment set to ‘None’
  • We’ve changed the way pipeline statistics are generated so that they’re much more clear

Bug fixes

  • Fixed bug with incorrect date of the last change to a directory or file in the Code tab. The date is generated with git log: sometimes a wrong parameter was applied and the last revision was not fetched, which caused the website to crash
  • Basic authentication for the HTTP Request action was only served in the POST method. Now the rest of methods is served as well
25 May 2017

Slack as Deployment Bot

Slack is hot 🔥.

Everybody knows what it is, almost everybody has already used it. Slack is the most popular notification action in Buddy, with over 24% of all (!) accounts using it. At this rate, the email and mobile notification will soon be passé, with Slackers taking over the world.

25 May 2017

New feature: AWS Lambda Deployment

Following the recent addition of the AWS CLI, Buddy is tightening the integration with Amazon services with the new Lambda deployment action.

AWS Lambda is a compute service that lets developers run code without provisioning or managing servers. All you need to do is deploy your function code, and AWS will take care of the rest. You can use it, eg. to scale images, run content analysis or make a backup of your site. It is a tool focused strictly at event-driven systems.

24 May 2017

New feature: Aurelia CLI

Widening the range of front-end tools, we’re happy to introduce Aurelia CLI to the list of actions.

Aurelia is a popular JavaScript client framework for mobile, desktop and web development. Lightweight and designed with a simple convention on mind, it frees developers from writing loads of configuration code, so they can focus on writing code practically in pure vanilla JS.

18 May 2017

Permissions in pipelines

Every member in the team has their own role. We can distinguish plenty of them: Junior Developer, Senior Developer, Frontend, Backend, DevOps, SysAdmin – you name it.

Each single role determines a member’s duties and permissions and is strictly based on the member’s skills. For instance, a Junior Developer shouldn’t have permissions to release the application to Production, but they should have permissions to deploy to the Dev server.