Skip to content

Commit 5d6b10e

Browse files
author
Vaughn Dice
authored
Merge pull request #362 from vdice/comp-release-job
docs(release_checklist.md): add brief description of <component>-release job
2 parents 3ea234c + 7f7a955 commit 5d6b10e

1 file changed

Lines changed: 3 additions & 2 deletions

File tree

src/roadmap/release-checklist.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ version of our release for testing. Here is the current process to do so:
106106

107107
# Step 3: Kick off Jenkins Jobs
108108

109-
Navigate to https://ci.deis.io/job/workflow-test-release/ and kick off a new job with appropriate build parameters filled out, i.e. `HELM_REMOTE_BRANCH=$WORKFLOW_RELEASE` and `RELEASE=$WORKFLOW_RELEASE_SHORT`
109+
Navigate to https://ci.deis.io/job/workflow-test-release/ and kick off a new job with the appropriate build parameters filled out, i.e. `WORKFLOW_BRANCH=release-$WORKFLOW_RELEASE`, `WORKFLOW_E2E_BRANCH=release-$WORKFLOW_RELEASE` and `RELEASE=$WORKFLOW_RELEASE_SHORT`.
110110

111111
As of this writing, the e2e tests in this job are run on a GKE cluster using default (minio) storage. To kick off the supported external storage permutations, run https://ci.deis.io/job/storage_backend_e2e/ w/ `STORAGE_TYPE` of 'gcs' and 'aws', along with the other
112112
values used in job above.
@@ -145,7 +145,8 @@ Amazon S3 |
145145

146146
- PR the fix, get it reviewed and merged into master of component repo(s)
147147
- git cherry-pick <issue_fix_sha> into the `release-$WORKFLOW_RELEASE` branch(es) of component repo(s)
148-
- update the appropriate component's `dockerTag` value in the release chart with the `git-<issue_fix_sha>` from the cherry-pick commit above.
148+
- the component's `<component>-release` [Jenkins job](https://ci.deis.io) watches for the push to the release branch and will trigger building and deploying the `git-<issue_fix_sha>` Docker image.
149+
- update the appropriate component's `dockerTag` value in the release chart with the `git-<issue_fix_sha>` as deployed above.
149150
- push updated chart change(s) to existing release branch and re-convene testing
150151

151152
When testing shows no further issues and the release chart is ready to ship, make sure the pull request is reviewed once more and merged before continuing.

0 commit comments

Comments
 (0)