You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: tekton/release-cheat-sheet.md
+37-23
Original file line number
Diff line number
Diff line change
@@ -12,24 +12,54 @@ the pipelines repo, a terminal window and a text editor.
12
12
13
13
1.[Install kustomize](https://kubectl.docs.kubernetes.io/installation/kustomize) if you haven't already.
14
14
15
-
1. Ensure the correct version of the release pipeline is installed on the cluster:
15
+
1. Select the commit you would like to build the release from (NOTE: the commit is full (40-digit) hash.)
16
+
- Select the most recent commit on the ***main branch*** if you are cutting a major or minor release i.e. `x.0.0` or `0.x.0`
17
+
- Select the most recent commit on the ***`release-<version number>x` branch***, e.g. [`release-v0.47.x`](https://github.com/tektoncd/pipeline/tree/release-v0.47.x) if you are patching a release i.e. `v0.47.2`.
18
+
19
+
1. Ensure the correct version of the release pipeline is installed on the cluster.
20
+
To do that, the selected commit should be checked-out locally
1. Choose a nameforthe new release! The usual pattern is "< cat breed > < famous robot >" e.g. "Ragdoll Norby". For LTS releases, add a suffix "LTS"inthe name such as "< cat breed > < famous robot > LTS" e.g. "Ragdoll Norby LTS". Use this command to generate a name that has not yet been used:
- Select the commit you would like to build the release from (NOTE: the commit is full (40-digit) hash.)
28
-
- Select the most recent commit on the ***main branch***if you are cutting a major or minor release i.e. `x.0.0` or `0.x.0`
29
-
- Select the most recent commit on the ***`release-<version number>x` branch***, e.g. [`release-v0.47.x`](https://github.com/tektoncd/pipeline/tree/release-v0.47.x) if you are patching a release i.e. `v0.47.2`.
52
+
1. Create a `release.env` file with environment variables forbash scriptsin later steps, and source it:
30
53
31
54
```bash
32
-
TEKTON_RELEASE_GIT_SHA=# SHA of the release to be released
55
+
cat <<EOF > release.env
56
+
TEKTON_VERSION= # Example: v0.69.0
57
+
TEKTON_RELEASE_GIT_SHA= # SHA of the release to be released, e.g. 5b082b1106753e093593d12152c82e1c4b0f37e5
58
+
TEKTON_OLD_VERSION= # Example: v0.68.0
59
+
TEKTON_RELEASE_NAME="Oriental Longhair Omnibot" # Name of the release
60
+
TEKTON_PACKAGE=tektoncd/pipeline
61
+
EOF
62
+
. ./release.env
33
63
```
34
64
35
65
1. Confirm commit SHA matches what you want to release.
@@ -103,15 +133,6 @@ the pipelines repo, a terminal window and a text editor.
103
133
104
134
1. The YAMLs are now released! Anyone installing Tekton Pipelines will get the new version. Time to create a new GitHub release announcement:
105
135
106
-
1. Choose a name forthe new release! The usual pattern is "< cat breed > < famous robot >" e.g. "Ragdoll Norby". For LTS releases, add a suffix "LTS"in the name such as "< cat breed > < famous robot > LTS" e.g. "Ragdoll Norby LTS". Browse [the releases page](https://github.com/tektoncd/pipeline/releases) or run this command to check which names have already been used:
0 commit comments