New features

• New action: Dockerfile Linter
• Sending commit statuses from synchronized repositories to Bitbucket

Improvements

• The fields Certificate authority, Client certificate and Client key in k8s actions now also support base 64 encoded values
• [Build action] [Run Docker container] From now on, you can not only mount the whole filesystem but also a specific path to the container

In Buddy you can configure delivery pipelines either through GUI or YAML. Until now, pipelines were defined in one file called buddy.yml and stored in the ROOT of our repository. However, there are users who have tens of pipelines in a single project (the current record holder has over 400!), and managing such large numbers through YAML can prove troublesome, to say the least.

Until now, the timeout for actions in Buddy was fixed permanently at 90 minutes. This means the action was automatically terminated if it was still in progress after an hour and a half. There were a few exceptions from the rule in which it was possible to set the timeout manually, e.g. HTTP or K8s apply actions . From this week onwards, you can do it in all actions in the system. The feature can be found in the Action tab:

New features

• [Action timeout] It is now possible to set a timeout for every action in the ‘Action’ tab. If an action fails to execute within the set time, the entire execution will be terminated
• From now on, you can now define pipelines not only in buddy.yml, but in any number of *.yml files in the .buddy folder

Improvements

• New default variables: $BUDDY_EXECUTION_TIME, $BUDDY_REPO_SSH_URL
• [Services] Improved logs for the beginning of the execution
• [AWS CLI] Changed the shell from SH to BASH

Bugfixes

• Fixed a bug with with actions moving to the end of the pipeline if they were updated via the REST API
• Fixed a bug with checking out faulty code from the repository to the filesystem if an error occured during submodule fetch

Improvements

• [Custom Services] The Image tag field now supports environment variables
• [Push Docker Image] The action does not clear dangling images anymore
• Variable suggestions in actions now involve action-specific variables
• Improved error handling when processing YAML
• From now on, a project owner can edit/delete a project within an hour from its creation even without admin privileges

Bugfixes

• [SSH] Fixed a bug with canceling the action in the ‘Run as a script’ mode not canceling script execution on the server
• Fixed a bug with links to new files directing users to the BASE branch instead of the HEAD branch when comparing branches

Unless you’re an assassin on a government contract, you need to be on Google if you run a business. This doesn’t mean just indexing your website: it means getting on the first page of search results. An important factor affecting the search engine position is how fast your website is loading. In other words, the better it’s optimized, the higher it displays on Google.

One of the basic optimization tips is compressing website images with third-party tools, a thing developers often do in their pipelines with Gulp/Grunt/npm scripts before the deployment. We’re excited to announce that Buddy now has a dedicated action allowing you to compress images without scripts and external libraries.

Last month our notification actions – Discord, Slack, Telegram and email – were upgraded with support for file attachments. However, in case of Discord, adding this feature required us to rewrite the whole action from scratch. The changes also cover defining the action with YAML and the API.

New features

• New action: Compress images
• New git-crypt actions: Lock and Unlock

Improvements

• From now on, settable variables are also exported in the SSH action (provided Only run as script option is toggled)
• Start times of build action services are now being logged

Bugfixes

• Fixed an issue with occasional errors during action termination

Improvements

• [Activity stream] Clicking a pipeline deletion event will produce the pipeline’s YAML configuration. This is useful if you want to restore a pipeline that was deleted.
• [Activity stream] Clicking a project deletion event will produce YAML configuration of all pipelines within this project.
• [Discord] The URL field now supports ENV VARs
• Build actions now support ENV VARs in the working dir & mount filesystem path fields

Bugfixes

• [Amazon S3] Fixed a bug with region support during the upload to an S3 bucket
• [HTTP] Fixed a bug with request logging occasionally crashing the action
• [Netlify] Fixed a validation bug when adding/updating the action with the REST API
• Fixed a bug with the execution message not being copied when cloning a pipeline
• Fixed a bug which prevented the workspace owner from transferring the ownership to another user

We’re excited to announce that Buddy now supports deployments to Netlify via Netlify’s CLI. In other words, you can build and test your frontend with Buddy and upload it to Netlify hosting, or run any command supported by the CLI. This was the most requested integration in the past couple of weeks – let us know what you want to see next in the comments or on our live-chat!