# Automatic Deployment at Shopify

DevFeed: [Automatic Deployment at Shopify](<https://devfeed.tech/articles/automatic-deployment-at-shopify-1298.md>)

Original publisher: [Read original article](<https://shopify.engineering/automatic-deployment-at-shopify>)

Author: Graeme Johnson

Published: 2016-10-19T17:00:00Z

Content type: article

Language: en

Sources: [Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering.md>), [Shopify Engineering - Shopify Engineering](<https://devfeed.tech/sources/shopify-engineering-shopify-engineering.md>)

Topics: [ci](<https://devfeed.tech/topics/ci.md>), [developer tooling](<https://devfeed.tech/topics/developer-tooling.md>)

Tags: [ci](<https://devfeed.tech/tags/ci.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [github](<https://devfeed.tech/tags/github.md>), [production](<https://devfeed.tech/tags/production.md>), [pull-request](<https://devfeed.tech/tags/pull-request.md>), [shopify](<https://devfeed.tech/tags/shopify.md>)

## AI overview

Shopify describes automating deployments after GitHub merges. Its pipeline builds a container, runs CI, batches merges, retests changes, and deploys them to production.

## Source excerpt

6 minute read Hi, I'm Graeme Johnson, and I work on Shopify's Developer Acceleration team. Our mission is to provide tools that let developers ship fast and safely. Recently we began shipping Shopify automatically as developers hit the merge button in GitHub. This removes the final manual step in our deploy pipeline, which now looks like this: Merge -> Build container -> Run CI -> Hit deploy button -> Ship to production We have invested a lot of engineering effort to make this pipeline fast enough to run end-to-end in about 15 minutes--still too slow for our taste--and robust enough to allow cancellation at any stage in the process. Automating the actual deploy trigger was the next logical step.