Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ONPREM-1771: document version skip to server 4.7 #9155

Merged
merged 5 commits into from
Jan 9, 2025
Merged

ONPREM-1771: document version skip to server 4.7 #9155

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9da2b79
server: document version skip to server 4.7
marcospereira-circleci Dec 19, 2024
3842f5d
server: also document skip in server 4.7 section
marcospereira-circleci Dec 19, 2024
7dc6cd6
server: upgrade path for server 4.6 docs
marcospereira-circleci Dec 20, 2024
add5377
Merge branch 'master' into marcospereira/server/upgrade-path
shellystuart Jan 9, 2025
f8c7add
server: remove outdated GKE warning for 4.5
shellystuart Jan 9, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions jekyll/_cci2/server/latest/installation/upgrade-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ This page describes the steps needed to upgrade your CircleCI server installatio
[#path]
== Upgrade paths

TIP: Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.3, 4.4, 4.5 and 4.6 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.
Expand Down
2 changes: 2 additions & 0 deletions jekyll/_cci2/server/v4.3/installation/upgrade-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,8 @@ This upgrade to v4.3 is a disruptive process and downtime is expected. A success
[#path]
== Upgrade paths

TIP: Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.3 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.
Expand Down
2 changes: 2 additions & 0 deletions jekyll/_cci2/server/v4.4/installation/upgrade-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ This page describes the steps needed to upgrade your CircleCI server installatio
[#path]
== Upgrade paths

TIP: Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.4 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.
Expand Down
4 changes: 2 additions & 2 deletions jekyll/_cci2/server/v4.5/installation/upgrade-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,13 +13,13 @@ noindex: true
:toc: macro
:toc-title:

CAUTION: If your CircleCI server installation is on GKE, do not upgrade to v4.5 at this time. GKE support will be announced in a future release.

This page describes the steps needed to upgrade your CircleCI server installation to v4.5.

[#path]
== Upgrade paths

TIP: Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.5 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.
Expand Down
2 changes: 2 additions & 0 deletions jekyll/_cci2/server/v4.6/installation/upgrade-server.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@ This page describes the steps needed to upgrade your CircleCI server installatio
[#path]
== Upgrade paths

TIP: Our general recommendation is not to skip releases when upgrading. However, we validated that **you can seamlessly upgrade directly from server 4.6 to server 4.7**. While future version skips may not be tested by CircleCI, this ensures a clear path to adopt server 4.7 and stay on a newly supported version.

We recommend that you **do not** skip releases when upgrading, however some patch releases can be skipped. Your upgrade path will depend on your current version, and the currently available version releases.

When upgrading from one minor version to the next, ensure your upgrade path includes the last patch release for your current minor version.
Expand Down