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:
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.
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!