shipit-engine

> Usually that was in the form of long-running network calls. That's why doing a network call to another service in the middle of a request is pretty much banned from the monolith. Anything that doesn't have a strict SLO is done from background jobs that can take longer, be retried etc. Now you mention FedEx so I presume you were working on the shipping service, which by essence is kind of an API bridge so it's probably why it was deemed acceptable there, but that's far cry from what a typical Rails app look like, except maybe in companies that do a lot of micro-services and are forced to do inline requests. > that's not a use case that Ruby/Rails are built to elegantly handle. I'd argue the contrary, the elegant way to handle this is to perform these calls from background jobs. Look at shipit [0] for instance, it's syncing with the GitHu

My team is evaluating different deployment tools to replace our homegrown solution. There are plenty of continuous integration tools (GitHub Actions, CircleCi, etc.), but adding deployment aware logic like canary deployments and having an audit log of deploys requires adding lots of code which I'd rather not maintain. I'm looking for tools focused on code deployment. A quick search turned up shipit (https://github.com/Shopify/shipit-engine) and teletraan (https://github.com/pinterest/teletraan). Are there other open-source deployment tools like those projects?

How does this compare to Shipit? https://github.com/Shopify/shipit-engine

From the previous discussion https://news.ycombinator.com/item?id=16166645 1. https://github.com/gocd/gocd - 6.1k stars 2. https://github.com/Shopify/shipit-engine - 1.2k stars 3. https://github.com/guardian/riff-raff - 252 stars 4. https://github.com/ankyra/escape - 201 stars 5. https://github.com/kiwicom/crane - 92 stars 6. https://github.com/tim-group/orc - 34 stars 7. https://github.com/wballard/starphleet - 19 stars (dead?) 8. https://spinnaker.io/

Sure my pleasure. > I like you enforce the commit/ticket relationship. Is this purely an agreed process or do you use other measures to keep things consistent? E.g. we typically add the ticket ref to each commit but at times that gets omitted. We're not enforcing it but we might in the future if the team grows and this gets out of hands. At the moment we're just reminding people that they should and it works great so far. > Would you mind expanding a bit on the things you enforce for each of your releases? It's still early but so far we check: - it's not friday afternoon, we want to avoid as much as possible to have issues on the weekend - it's not out of office hour - we're still all on the same time zone - there's no lock (we can lock the release in case something goes wrong) - there's no schema migration. If there is we remind you how

It's better to have an activity log of your deployments, that way by querying what commit is currently in production you can compare it with the log and know what actually commit range was deployed. There is many tools to do that, e.g. - Shopify's Shipit: https://github.com/shopify/shipit-engine (author here) - Zendesk's Samson: https://github.com/zendesk/samson - Netflix's Spinnaker: http://techblog.netflix.com/2015/11/global-continuous-delivery-with.html - Yahoo's Screwdriver: https://yahooeng.tumblr.com/post/155765242061/open-sourcing-screwdriver-yahoos-con… - Instagram's Sauron: https://engineering.instagram.com/continuous-deployment-at-instagram-1e18548f01d1#… And the list goes on.