From 1dd1dc8d90fe97f5156448e538ce00b32f08184b Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Fri, 28 Jul 2017 11:19:16 +0100 Subject: [PATCH] add instructions for updating Weave Cloud Prod --- Release-Process.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/Release-Process.md b/Release-Process.md index b9c8ebd..5d4121b 100644 --- a/Release-Process.md +++ b/Release-Process.md @@ -144,6 +144,12 @@ If you don't need sudo to run Docker commands, you should do $ env GITHUB_TOKEN=xxx SUDO= bin/release publish ``` +The [manually](https://github.com/weaveworks/scope/issues/2762) push the release to quay.io with something like +``` +$ docker tag weaveworks/scope:1.6.0 quay.io/weaveworks/scope:1.6.0 +$ docker push quay.io/weaveworks/scope:1.6.0 +``` + ## Merge Merge the release branch to master. @@ -152,3 +158,8 @@ Merge the release branch to master. Go to [https://checkpoint-api.weave.works/admin](https://checkpoint-api.weave.works/admin) and fill in the details of the release for **both for the scope-app and scope-probe products** so that users can be automatically informed of a new version being available. +## Bump the scope probe version in Weave Cloud Prod + +(Weave Cloud Prod probes should always run the most recent release) + +You should know how to do that. Use the specific version, e.g. '1.6.0' rather than a commit hash. \ No newline at end of file