Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
7d7aa9ec
Commit
7d7aa9ec
authored
Nov 07, 2015
by
k8s-merge-robot
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #16939 from ihmccreery/versioning-cleanup
Auto commit by PR queue bot
parents
4e39dd4b
e5449f7d
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
18 additions
and
12 deletions
+18
-12
common.sh
cluster/common.sh
+12
-6
releasing.md
docs/devel/releasing.md
+6
-6
No files found.
cluster/common.sh
View file @
7d7aa9ec
...
@@ -24,11 +24,17 @@ KUBE_ROOT=$(dirname "${BASH_SOURCE}")/..
...
@@ -24,11 +24,17 @@ KUBE_ROOT=$(dirname "${BASH_SOURCE}")/..
DEFAULT_KUBECONFIG
=
"
${
HOME
}
/.kube/config"
DEFAULT_KUBECONFIG
=
"
${
HOME
}
/.kube/config"
# KUBE_VERSION_REGEX matches things like "v1.2.3"
# KUBE_RELEASE_VERSION_REGEX matches things like "v1.2.3" or "v1.2.3-alpha.4"
KUBE_VERSION_REGEX
=
"^v(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)$"
#
# NOTE This must match the version_regex in build/common.sh
# kube::release::parse_and_validate_release_version()
KUBE_RELEASE_VERSION_REGEX
=
"^v(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)(-(beta|alpha)
\\
.(0|[1-9][0-9]*))?$"
# KUBE_CI_VERSION_REGEX matches things like "v1.2.3-alpha.4.56+abcdefg"
# KUBE_CI_VERSION_REGEX matches things like "v1.2.3-alpha.4.56+abcdefg" This
KUBE_CI_VERSION_REGEX
=
"^v(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)-(.*)$"
#
# NOTE This must match the version_regex in build/common.sh
# kube::release::parse_and_validate_ci_version()
KUBE_CI_VERSION_REGEX
=
"^v(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)
\\
.(0|[1-9][0-9]*)-(beta|alpha)
\\
.(0|[1-9][0-9]*)(
\\
.(0|[1-9][0-9]*)
\\
+[-0-9a-z]*)?$"
# Generate kubeconfig data for the created cluster.
# Generate kubeconfig data for the created cluster.
...
@@ -261,7 +267,7 @@ function set_binary_version() {
...
@@ -261,7 +267,7 @@ function set_binary_version() {
#
#
# Assumed vars:
# Assumed vars:
# KUBE_VERSION
# KUBE_VERSION
# KUBE_VERSION_REGEX
# KUBE_
RELEASE_
VERSION_REGEX
# KUBE_CI_VERSION_REGEX
# KUBE_CI_VERSION_REGEX
# Vars set:
# Vars set:
# KUBE_TAR_HASH
# KUBE_TAR_HASH
...
@@ -273,7 +279,7 @@ function tars_from_version() {
...
@@ -273,7 +279,7 @@ function tars_from_version() {
if
[[
-z
"
${
KUBE_VERSION
-
}
"
]]
;
then
if
[[
-z
"
${
KUBE_VERSION
-
}
"
]]
;
then
find-release-tars
find-release-tars
upload-server-tars
upload-server-tars
elif
[[
${
KUBE_VERSION
}
=
~
${
KUBE_VERSION_REGEX
}
]]
;
then
elif
[[
${
KUBE_VERSION
}
=
~
${
KUBE_
RELEASE_
VERSION_REGEX
}
]]
;
then
SERVER_BINARY_TAR_URL
=
"https://storage.googleapis.com/kubernetes-release/release/
${
KUBE_VERSION
}
/kubernetes-server-linux-amd64.tar.gz"
SERVER_BINARY_TAR_URL
=
"https://storage.googleapis.com/kubernetes-release/release/
${
KUBE_VERSION
}
/kubernetes-server-linux-amd64.tar.gz"
SALT_TAR_URL
=
"https://storage.googleapis.com/kubernetes-release/release/
${
KUBE_VERSION
}
/kubernetes-salt.tar.gz"
SALT_TAR_URL
=
"https://storage.googleapis.com/kubernetes-release/release/
${
KUBE_VERSION
}
/kubernetes-salt.tar.gz"
elif
[[
${
KUBE_VERSION
}
=
~
${
KUBE_CI_VERSION_REGEX
}
]]
;
then
elif
[[
${
KUBE_VERSION
}
=
~
${
KUBE_CI_VERSION_REGEX
}
]]
;
then
...
...
docs/devel/releasing.md
View file @
7d7aa9ec
...
@@ -178,8 +178,8 @@ release/cut-official-release.sh "${VER}" "${GITHASH}"
...
@@ -178,8 +178,8 @@ release/cut-official-release.sh "${VER}" "${GITHASH}"
This will do a dry run of:
This will do a dry run of:
1.
do a series of commits on the release branch for
`vX.Y.Z-beta`
;
1.
do a series of commits on the release branch for
`vX.Y.Z-beta
.W
`
;
1.
mark the
`vX.Y.Z-beta`
tag at the beta version commit;
1.
mark the
`vX.Y.Z-beta
.W
`
tag at the beta version commit;
1.
prompt you to do the remainder of the work, including building the
1.
prompt you to do the remainder of the work, including building the
appropriate binaries and pushing them to the appropriate places.
appropriate binaries and pushing them to the appropriate places.
...
@@ -209,9 +209,9 @@ This will do a dry run of:
...
@@ -209,9 +209,9 @@ This will do a dry run of:
1.
do a series of commits on the branch for
`vX.Y.Z`
;
1.
do a series of commits on the branch for
`vX.Y.Z`
;
1.
mark the
`vX.Y.Z`
tag at the release version commit;
1.
mark the
`vX.Y.Z`
tag at the release version commit;
1.
do a series of commits on the branch for
`vX.Y.(Z+1)-beta`
on top of the
1.
do a series of commits on the branch for
`vX.Y.(Z+1)-beta
.0
`
on top of the
previous commits;
previous commits;
1.
mark the
`vX.Y.(Z+1)-beta`
tag at the beta version commit;
1.
mark the
`vX.Y.(Z+1)-beta
.0
`
tag at the beta version commit;
1.
prompt you to do the remainder of the work, including building the
1.
prompt you to do the remainder of the work, including building the
appropriate binaries and pushing them to the appropriate places.
appropriate binaries and pushing them to the appropriate places.
...
@@ -245,8 +245,8 @@ This will do a dry run of:
...
@@ -245,8 +245,8 @@ This will do a dry run of:
1.
mark the
`vX.(Y+1).0-alpha.0`
tag at the given git hash on
`master`
;
1.
mark the
`vX.(Y+1).0-alpha.0`
tag at the given git hash on
`master`
;
1.
fork a new branch
`release-X.Y`
off of
`master`
at the given git hash;
1.
fork a new branch
`release-X.Y`
off of
`master`
at the given git hash;
1.
do a series of commits on the branch for
`vX.Y.0-beta`
;
1.
do a series of commits on the branch for
`vX.Y.0-beta
.0
`
;
1.
mark the
`vX.Y.0-beta`
tag at the beta version commit;
1.
mark the
`vX.Y.0-beta
.0
`
tag at the beta version commit;
1.
prompt you to do the remainder of the work, including building the
1.
prompt you to do the remainder of the work, including building the
appropriate binaries and pushing them to the appropriate places.
appropriate binaries and pushing them to the appropriate places.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment