diff options
| author | Tim Smith <tsmith@chef.io> | 2019-06-11 13:19:31 -0700 |
|---|---|---|
| committer | Tim Smith <tsmith@chef.io> | 2019-06-11 13:19:31 -0700 |
| commit | 86ccff25f80893b2faaaf5cbccbdede07c89ca64 (patch) | |
| tree | 5ed580c2ee1eecee9542f83287d0191d8f922db6 | |
| parent | 5e5a57067e672eaea4504bb0dcf7115d565a6bd6 (diff) | |
| download | chef-86ccff25f80893b2faaaf5cbccbdede07c89ca64.tar.gz | |
Link to the release doc from the build / test doc
Signed-off-by: Tim Smith <tsmith@chef.io>
| -rw-r--r-- | docs/dev/design_documents/how_chef_is_tested_and_built.md | 6 |
1 files changed, 2 insertions, 4 deletions
diff --git a/docs/dev/design_documents/how_chef_is_tested_and_built.md b/docs/dev/design_documents/how_chef_is_tested_and_built.md index fabcc52891..94fbaa8051 100644 --- a/docs/dev/design_documents/how_chef_is_tested_and_built.md +++ b/docs/dev/design_documents/how_chef_is_tested_and_built.md @@ -1,4 +1,4 @@ -# How Chef is Tested and Built +# How Chef Infra Client is Tested and Built This document describes the process that a change flows through from opened PR to omnibus build in our current channel. @@ -37,6 +37,4 @@ Once the builds complete, Jenkins will move to the test phase where each of thes ## Releasing Chef -Once a build has been blessed by our Jenkins gauntlet and everyone has agreed that we are ready to release, an artifact can be promoted from current to stable channels via Expeditor in Slack: - -``/expeditor promote chef/chef:master 14.6.47`` +Once a build has been blessed by our Jenkins gauntlet and everyone has agreed that we are ready to release, an artifact can be promoted from current to stable channels. For the complete release process see [Releasing Chef Infra Client](../how_to/releasing_chef_infra.md) |