Every member in the team has their own role. We can distinguish plenty of them: Junior Developer, Senior Developer, Frontend, Backend, DevOps, SysAdmin – you name it.
Each single role determines a member’s duties and permissions and is strictly based on the member’s skills. For instance, a Junior Developer shouldn’t have permissions to release the application to Production, but they should have permissions to deploy to the Dev server.
Google developers: you can clear your CDN cache on every deployment with the new purge action
Google CDN is one of the Content Delivery Networks. That means, when a user opens the website, the files are served from the closest server location which shortens the time required to open your website.
- New action: Google CDN Invalidation
Pipelines in Buddy are flexible enough to reproduce almost every type of workflow. Here are the three most popular use cases:
- Delivery – used to upload repository files or compiled app to the server on every push to branch, recurrently at a given time, or manually on click.
- Continuous Integration Server – used to run unit and integration tests on every push to repository and send notifications if the tests have failed
- Monitoring – used to check the status of website or server on given intervals and send a message in case it goes down.
In this article we’ll cover practical use of the new EB monitoring action in the context of existing delivery pipelines.
Every developer in the world knows exactly what AWS is. So does Buddy: it even has a separate section for Amazon services only. You can, for instance, upload a new version of the application to Elastic Beanstalk, deploy files to S3 or launch a Lambda function.
Following the Cloudflare integration released 4 weeks ago, we’re happy to announce BuddyWorks now officially supports AWS CloudFront
AWS CloudFront is a Content Delivery Network that shortens the time required to access your website.
Atomic deployments are the first in the series of pipeline templates that we introduced to Buddy.
In short, they allow you to update your website with zero downtime by uploading the files a cache directory on the server and switching the symlink of the web server to the new version when everything’s finished.
Recently we’ve modified the template by adding a feature that lets you define how many website versions you want to keep on the server.
We’re excited to announce that private repositories are now supported by BuddyWorks!
This means you can hook up Buddy with repositories on your private Git server, as well any other external Git provider, including:
- Visual Studio Team Services
All you need to do is provide configuration details of your repo + set up a web hook in your version control that will automatically refresh the list of commits in Buddy and trigger the deployments:
So, if you guys know of any developer who couldn’t use BuddyWorks because it didn’t support their Git provider, do not hesitate and spread the good news! 🙌