Wildcard patterns let you specify which branches will trigger the pipeline execution. This feature is especially useful for testing and deploying multiple branches on development servers.
- New build action: Ember CLI
- New transfer action: Deploy to AWS CodeDeploy
- Static site generators: Jekyll, Hugo, Hexo & Middleman
- New build actions: Meteor and .NET Core
- Deployment to Google App Engine
- Support for builds and deployments from private SSH submodules
In response to demand from the web development community we’re happy to bring you a series of build actions for popular static site generators:
- Jekyll - popular blog-aware static site generator written in Ruby
- Hexo - fast, simple and powerful blog framework for markdown written posts
- Hugo - flexible framework with many formats ideal for blogs, docs, portfolios and more
- Middleman - static site generator with modern web development tools and shortcuts
Following GCE action, we’re expanding our Google integration further with deployments to the Google App Engine.
Google App Engine is a cloud platform for developing and hosting web applications in Google-managed data centers. Sanboxed and run across multiple servers, the apps in the Engine are automatically scaled with more resources being allocated to them should the number of requests increase.
With .NET builds and Azure deployments already being available in Buddy for some time, we’re happy to announce the .NET Core build action.
.NET Core is a cross-platform (Windows, MacOS, Linux) framework optimized for open-source development and flexible deployments, maintained by Microsoft and the .NET community on GitHub.
We’re happy to announce you can now use folders to manage your pipelines. This feature comes handy if you’d like to organize your pipelines by environment (development, staging, production).
To create a folder, go to the Pipelines and click the option in the right column, type the name of the folder and select the pipelines that you want to include:
Editing Folder Settings
You can edit folder details by hovering mouse pointer over the folder name and clicking the edit option. Note that once you create a new folder, the remaining pipelines will be automatically put into a General folder. This folder cannot be edited and will disappear if the custom folders are removed.
Responding to your requests, one of the most popular actions has just got an upgrade with new functionalities. For Buddy newcomers, the action is available in the DevOps section of the action list:
Not Only POST
With only POST requests previously available, the HTTP action now supports PUT, PATCH, GET & DELETE.
For POST, PUT & PATCH payload you can use these variables.
Along with the payload you can now also send custom headers. Just click More options in the action details and add however many headers you need:
The ticker notifications in Buddy has been deprecated and is no longer available. At the moment, only desktop notifications are enabled.
Buddy has a special feature that lets you track only what’s important for you: following items. Whenever something happens in the item that you follow (repository or pipeline), a message will appear in the ticker menu:
- New functionalities in the HTTP Request action: PUT/PATCH/GET/DELETE methods, Custom headers and HTTP Basic Authorization
- Folders for pipelines
- Desktop notifications