Although Buddy’s actions are preconfigured, this doesn’t mean it gives you any less control over your workflow. In fact, each action can be fully modified, allowing you to change the Docker image, install packages required by your app, attach databases, and so on.
- [HTTP request] You can now set a timeout in the action
- [YAML] When switching the project from GUI to YAML Buddy will now automatically scan all branches (until now you had to push changes in the repo to process them from yaml)
- [Env Vars] Improved support for environment variables when testing an action in a pipeline
- [K8s] Updated kubectl version to 1.12.0 in all K8s actions
This week brings good news for developers orchestrating containers on AWS clusters: Buddy now officialy supports Amazon EKS!
In other words, if Jeff Bezos is your man and you often run
kubectl apply or
kubectl set image, you can finally benefit from the blessings of Buddy’s automation.
Buddy has always been about power and flexibility. One of the things that you lacked was the ability to use the artifacts from one pipeline in another. We’re happy to announce you can now do this with the dedicated Copy Files action.
- New action: Copy files between pipelines
- Exclude files from ignore paths in deployment actions
- [Amazon EKS] Automate Kubernetes deployment on the AWS infrastructure
- [ENV VARs] You can now add descriptions to the variables and preview their basic information in a tooltip for easier management
- [Trigger condition] Run actions only if the variable doesn’t contain a specific string
- The tag list on the ‘Code’ and ‘Run pipeline’ views is now displayed in reverse alphabetic order so that the newest tags are always on top
- [AWS] You can now deploy ZIP, WAR and JAR packages in the Lambda and Elastic Beanstalk actions. If the path provided doesn’t contain any packages, Buddy will prepare a zipped package with the contents of the directory
- [DigitalOcean] New regions added to the Cloud Object Storage deployment action
- The ‘Failed’ status on the Pass Params action view is now properly served
Buddy automatically sends pipeline status to GitHub and GitLab. Setting up a single pipeline with a wildcard
* mode will test code in all your branches and give a corresponding status:
- [Code Review] Send notifications to GitHub/GitLab. Disable the option if required
- [Docker Build] You can set the
--targetparameter in the Docker Build action. When building a Dockerfile with multiple build stages,
--targetcan be used to specify an intermediate build stage by name as a final stage for the resulting image. Commands after the target stage will be skipped”
- [Android] Updated library used to publish to Play Store
- [ENV VARs] Added auto-resize on the value input when adding or editing a variable
- [API/YAML] You can now define folders for pipelines with API/YAML
- [AWS CloudFront] Fixed a bug with the action failing if there were more than 3000 items in the changeset (they are now sent in packages of 3k)
- [Environment Variables] Deleted a new line char at the end of
$BUDDY_EXECUTION_REVISION_MESSAGE. Thanks for the heads up, John!
- [Google Cloud Storage] Fixed a bug with the action ending as failed when the changeset wanted to delete files that didn’t exist in the GCS
- [Datadog] You can now choose NA and EU region
- [AWS CLI] We’ve added a possibility to choose between BASH and SH shell what allows you to execute more advanced scripts
- [AWS] Improved error handling in CloudFront and Amazon actions
Buddy is a smart tool that lets you build and deploy your web projects. Before the application is deployed to the server, however, it is first tested in preconfigured Docker containers. Some of the tests, e.g. integration, E2E or Selenium, require a fully operational application with things like a database and session storage.
Buddy supports this functionality with microservices activated in build actions:
- New options in database services (MySQL, Postgres, MariaDB): it is now possible to seed databases and create the default database when starting up the service
- By default, Heroku and Git Push actions make a push to the specified remote with the
--forceflag applied. You can now turn the flag off in ‘More Options’ of both actions
- AWS Elastic Beanstalk & AWS CLI now use Ubuntu 18.04 with Python 3.6 installed (upgraded from 16.02 and Python 2.7). This has solved issues with coding special characters
- Improved service of new line in attachments in the Slack action