3 ms·
For work, we use Concourse-CI self-hosted on EC2 using this script[0]. We have blue-green deploys to Pivotal Web Services (PWS) which is hosted CloudFoundary in
by karmakaze 8y ago
For work, we use Concourse-CI self-hosted on EC2 using this script[0]. We have blue-green deploys to Pivotal Web Services (PWS) which is hosted CloudFoundary in AWS. We've written our own blue-green deployment scripts for Spring Boot, Node.js/React/Vue, and Python. We also have a pipeline for deploying directly to EC2 Autoscaling groups.
We have a Go service that is deployed directly to EC2 with a Makefile from its source repo. We deploy it so rarely that we haven't made a pipeline.
The deployment script is used to deploy first to a 'staging' environment and if all is well, a manual trigger to continue deploying the service to production. These deployments run from the 'master' branch from Github repos. We also have 'dev' branches that deploy to a separate dev environment for ad-hoc use for dev/integration.
Databases are PostgreSQL in AWS RDS with Liquibase used for migrations.
When performing a blue-green deployment to each environment, the test suite is run against the 'new' blue/green deployment. After passing this suite it becomes the current version in the environment and an additional 'Journey Test' sequence is run which verifies that the top 10 actions work as designed. We also run a 'Health Check' of the current production environment using the journey tests every 10 minutes.
[0] https://github.com/karmakaze/concourse-ec2 https://github.com/karmakaze/concourse-ec2
For personal projects, I've used Netlify for static sites, or webhooks/polling of Github/Gitlab repos to update prod deployments as well as a Makefile 'deploy-prod' target from the project repo.