From 8396b2bc8ff001fdbc71bbbb5b6caf33c61d8f83 Mon Sep 17 00:00:00 2001 From: Jordan Liu Date: Sat, 11 Apr 2020 20:45:22 -0500 Subject: [PATCH] "artefact" to "artifact" (#38528) --- docs/devops.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/devops.md b/docs/devops.md index febbd939bb..eeb4777835 100644 --- a/docs/devops.md +++ b/docs/devops.md @@ -114,7 +114,7 @@ Currently, only members on the developer team can push to the production branche The above steps will automatically trigger a run on the build pipeline for the `production-staging` branch. Once the build is complete, the artifacts are saved as `.zip` files in a cold storage to be retrieved and used later. -The release pipeline is triggered automatically when a fresh artefact is available from the connected build pipeline. For staging platforms, this process does not involve manual approval and the artifacts are pushed to the Client CDN and API servers. +The release pipeline is triggered automatically when a fresh artifact is available from the connected build pipeline. For staging platforms, this process does not involve manual approval and the artifacts are pushed to the Client CDN and API servers. > [!TIP|label:Estimates] > Typically the build run takes ~20-25 minutes to complete followed by the release run which takes ~15-20 mins for the client, and ~5-10 mins for the API to be available live. From code push to being live on the staging platforms the whole process takes **~35-45 mins** in total.