We’re excited to announce that after six months of work we have released a brand new documentation for Buddy. With the service growing at insane speed and new features released every week, the docs in their current form were no longer serving their purpose, especially for experienced developers looking for specific features, or those having a hard time trying to look things up.
- [Kubernetes] The ‘Run kubectl’ action now supports
- [Buddy Enterprise] - standalone-specific settings (resources, network, applications) have been moved from workspace preferences to the new settings tab [
- [Rsync] Improved support of ed25519 keys
- [YAML] Improved support of the
– [Pipeline settings] New option: Ignore pipeline on project status. Upon selection, the status of the pipeline will not affect the status of the entire project
- [Pipeline settings] You can now define the default execution message displayed on the activity streams
- [Google Function Deploy] New runtimes have been added
- If the execution was run by a different pipeline, the activity feed will display the pipeline icon instead of an avatar
- The ‘Request limit’ field in invalidation actions (AWS CloudFront, Cloudflare, DigitalOcean CDN, Google CDN) is now displayed only if ‘Purge mode’ is different than ‘Purge everything’
- New action: DigitalOcean CDN
- [Custom services] New option: Wait for custom service daemon on specified port
- [REST API] It is now possible to clone and export pipelines from your projects
- The list of executions now displays the total execution time
- Execution details now display execution time for each action
- Activity streams now display the YAML of the deleted pipeline
- Improved error support in environment preparation
- Adding group users to projects has been optimized
- Trigger condition on paths now supports environment variables
- [Telegram] It is now possible to send file attachments from the filesystem
- [Email notification] It is now possible to send file attachments from the filesystem (max 10 MB)
- [Discord] It is now possible to send multiple attachments from the filesystem (previously the limit was 1)
- [ZIP] If the target path does not exist in the filesystem, it will be created during the execution
- [Buddy Enterprise] The limit of services in build actions has been increased to 20
- Added request limit to invalidation actions (AWS CloudFront, CloudFlare, Google CDN). From now on, if the number of files sent for validation is higher than the set limit - all the files will be invalidated.
- Added the support for multiline comments in the executions
- Users can now change the ‘Run next action parallel’ flag in the action settings
- [Custom Services] Added more detailed logs in case the service has failed to start
- [Firebase] You can now select the version of and Node and Firebase CLI in the action details
- [Git Push] Fixed a bug with the ‘Git Push’ action failing if the commit message contained certain special symbols
- [AWS ECR] Pushing an image to a registry with a large number of repositories (>100) is no longer causing issues
- [Google Cloud Storage] Fixed a bug with cache control not being generated in the YAML generator
- Users will no longer encounter errors when pushing a repository via HTTPS
- Users will no longer encounter errors when opening an empty file during repository browse
- Fixed a bug with deleting an action causing errors if the action was in parallel mode
- Users with 2FA enabled were not asked for the authorization code when resetting the password - fixed
Continuous Integration and Delivery is all about simplicity. It’s not about configuring the process just for the sake of it—it’s about stripping it down to the bare minimum and adding new steps only if necessary. This approach guided us during Buddy’s development – to create a tool simple enough for every developer to embrace automation and expand the process at any point. It also applies to the very first step, which is setting up an account: a task that defines the whole user experience onwards.
- Learn how to dockerize and test a PHP application on every change to code
- [Wait for approval] You can now see who and when approved the execution in the action logs
- [Copy files] Improved display of the pipeline’s source for users who don’t have access to it
- [Run next pipeline] Improved display of the pipeline to execute for users without appropriate permissions
- [Copy files] It is now possible to copy hidden files
- Improved error handling when synchronizing GitHub projects
- Improved error handling when selecting a path on the remote server
- Improved VAT-ID validation
- [Copy files] Fixed a bug with the action failing if it was executed by a user without permissions to the source pipeline
- [Telegram] It was possible to send a notification without any content which caused the action to fail. We have added a validation to prevent it
- [Cloudflare] Fixed a bug with the base URL getting inappropriately overwritten after loading zones
- From now on, you can specify which ACL you want to set for files uploaded in the S3 action
- Fixed a bug with empty lines in build action commands resulting in an error during pipeline import
- If a pipeline was in a folder, cloning it between projects caused errors - fixed
Docker flows through the veins of Buddy. It is the fuel that makes our builds run so smooth and simple:
- First, it launches an isolated container.
- Second, it downloads dependencies and caches them in the pipeline’s filesystem mounted to the container.
- Third, it runs build commands on repository files.
- Fourth, it exports the artifacts to the filesystem nad kills the container.
By default, Docker containers are run with the user defined in the image. However, some of you were requesting an option to change the user – and this is what we are delivering this week.