- Deployment Pipeline (re-instate)
- CI (shippable or semaphore) triggers pipeline on successful master build
- Probably 'Go' - has misgivings but does the job for now
- builds and pushes docker container artifact
- deploy to staging
- smoke test
- acceptance test
- Deploy to prod (auto-deploy can be optional e.g. supporter)
- smoke test
- CI (shippable or semaphore) triggers pipeline on successful master build
- Rollback on failure
#The Winds of Change
Here at Everyday Hero we’re a Ruby shop. We love Ruby. Ruby is great. We are however, starting to experiment with introducing other programming languages and technologies for our backend services into our repertoire. One of our new micro-services has been started in Elixir. In this post I’ll discuss our reasons for looking beyond Ruby at another programming language and technology.
Being a Ruby shop, nearly all our applications are written in Ruby - our oldest apps were started way back on Ruby 1.8 and Rails 1.0, and we now have a fleet of apps that keep up with the latest Ruby and Rails versions, as well as smaller services that use other frameworks like Sinatra or Napa. We have a long history (in Ruby terms) with this technology set. ###Why Ruby is Great I still remember the excitement I felt when I discovered Ruby (and Rails) in about 2006, and I’m pretty sure the reason Ruby gained such popularity is because so many developers felt the same thing. Ruby brought the joy back into prog