December 15, 2016
Buddy's 2016 Recap
It's been a year since we launched Buddy and, oh boy, what a year it was! Below you will find a recap of 2016 that will show you how the service evolved month by month, feature by feature.
January: Docker-based build actions
Run your builds in isolated Docker containers with pre-installed languages and frameworks.
February: Filesystem for pipelines
Compile files, generate artifacts and store static files in pipeline-specific cache folders.
March: Wildcards for pipelines
Define trigger mode patterns to test and deploy multiple branches at once.
April: Actions triggering on if conditions
Use conditional actions to send custom notifications on failed builds and deployments.
May: Services for containers
Attach services to build actions: MySQL, MongoDB, Elastic, Postgres, Redis, MariaDB & Memcached.
June: Buddy GO
Store code and run builds and deployments on your own server with the official self-hosted version of Buddy.
July: Recurring executions for pipelines
Run integration tests and monitor your websites and servers in specified time intervals.
August: Deploy anywhere, anytime
Deploy your apps to AWS Elastic Beanstalk, Google App & Cloud Engines and Microsoft Azure on a single push to branch.
New deployment actions
September: Environment variables
Store and manage logins, passwords and parameters for easy access from any input in the service.
October: Pipeline badges
Embed images to show the status of your builds on a website or in a README file.
November: Amazon Love. Expanded
Run code in AWS Lambda, Deploy Docker images to ECR, and update your EC2 instances with CodeDeploy.
New Amazon actions
December: Static site generators
Develop blogs, documents and portfolios with a series of the most popular static site generators.
New Amazon actions
Customer Success Manager