Our stacks:
Tests
Monitoring
Deployment
All our static assets are in another repo and we've set up Webhooks which pulls it to the server on every push to master (or successful pull-request).
Siddarthan Sp's answer has made me consider Buddy!
To automate deployments & integration testing you can use various CI/CD tools like jenkins, shippable & CircleCI. I personally like shippable as it package every feature a DevOps might need, For example automated deployments, blue-green deployments, smart-scaling & feature rich CI platform which gives you all insights about code like unit test results and code coverage reports.
Some of the DevOps automation tools which are worth giving a try are
among these, I guess Shippable is the best value for money and worth trying and I guess their strongest point is they have recently launched their Server product which is really good. And one of their key aspect is response time for tickets, its amazing I guess they have 24*7 support. They also give full assistance in configuring your builds with Shippable.
For CI purpose we prefer to use Travis CI for a long time and it is really good. But recently used 'Shippable' and it looks good and they are adding a lot features. Codeship is also best.
Hi there
There' obviously the CI tool (CircleCI in our case, but there are so many out there).
(Most of our code is NodeJS, and we use the usuall tools there with mocha, chai, ...)
As we're in the process of preparing moving a lot to Kubernetes, we're investing in Helm right now to manage releases
All our logs are sent to Loggly, on which we do have (too?) many alerts
Our metrics (from web servers, workers, but also db servers, nginx, rabbitmq...) are also sent to Datadog, on which we have some other alerts
All alerts are sent to a dedicated Slack channel.
Critical alerts also triggered Pagerduty tickets for the on-call team. (We're a small team, so there's only a single on-call group)
Then I'd like to mention some other tools we built/leverage to help us doing
AWS Lambda can be triggered by CLoudwatch Cron events, which makes a super cheap (as in almost free), secure and resilient way to run administrative cron task. In this case, this Cloudwtach cron event trigger a lambda which start a on-off task in ECS (which we'll probably later move to a Kubernetes Job). This weekly job is built in-house (Python and Docker there) to shallow-clone all the repositories from our org, and run vulnerability scans against them (with Snyk and NSP), format the reports and post them to Slack. We used this approach to get a cheap and 0-maintenance way to scan any repos, public or private, and make sure even the new repo created will be scanned, without the need to do any setup.
Bottom line for your automation needs: Cloudwatch scheduled events are usually overlooked, but imho Cloudwtach scheduled events+lambda should replace traditional cron jobs most of the time!
There's probably many other things I take for granted and I forget to mention there,
We at the moment use Gitlab but i would say we are at very nascent stage in DevOps automation. For starters it is a good option and has an open source version that can be self hosted and is free.
We use Buddy on premise, at the moment. We did consider Shippable, Codeship and Jenkins, but we needed a free and an easy to maintain on-premise solution.
This is our story on why we chose buddy.
Rueben Ramirez
burner of poptarts, breaker of things