JKNS-630: Support Matrix for OpenShift Jenkins releases #91968
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
do-not-merge/work-in-progress
sghai
reviewed
Apr 10, 2025
k37y
changed the title
openshift-ci-robot
added
the
jira/valid-reference
|
@k37y: This pull request references JKNS-630 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the ticket to target the "4.19.0" version, but no target version was set. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
removed
the
do-not-merge/work-in-progress
|
/label peer-review-needed |
openshift-ci
bot
added
the
peer-review-needed
|
/label peer-review-in-progress |
openshift-ci
bot
added
peer-review-in-progress
cbippley
reviewed
Apr 10, 2025
|
/label peer-review-done |
openshift-ci
bot
added
peer-review-done
- Add Support Matrix for OpenShift Jenkins releases - Add FAQ Signed-off-by: Vinu K <[email protected]>
|
@k37y: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
@cbippley, thanks for the review. I have added all the changes. |
|
/label merge-review-needed |
openshift-ci
bot
added
the
merge-review-needed
jeana-redhat
added
the
merge-review-in-progress
There was a problem hiding this comment.
There are several instances of OpenShift in plain text. Typically, these should all be replaced by {product-title}. I notice some of these instances are matching the use in the linked KB article, so I guess it's better to be consistent. I have suggested replacements where it's not in direct conflict with the article.
Related question: is "OpenShift Jenkins" a product name?
| @@ -49,3 +49,44 @@ $ oc import-image jenkins-agent-nodejs -n openshift | |||
| ---- | |||
| $ oc import-image jenkins-agent-maven -n openshift | |||
| ---- | |||
|
|
|||
| .What is the Jenkins support matrix for OpenShift, including supported versions and architectures? | |||
There was a problem hiding this comment.
This seems to answer a different question than is written, maybe:
Suggested change
| .What is the Jenkins support matrix for OpenShift, including supported versions and architectures? | |
| .What {product-title} architectures and versions does Jenkins support? |
| - `ppc64le` | ||
| - `s390x` | ||
|
|
||
| However, for OpenShift Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. Refer to link:https://access.redhat.com/articles/7115356[OpenShift Jenkins Support Matrix] for more information. |
There was a problem hiding this comment.
Suggest either using the attribute:
Suggested change
| However, for OpenShift Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. Refer to link:https://access.redhat.com/articles/7115356[OpenShift Jenkins Support Matrix] for more information. | |
| However, for {product-title} Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. For more information, see link:https://access.redhat.com/articles/7115356[Support Matrix for OpenShift Jenkins releases]. |
or removing the name:
Suggested change
| However, for OpenShift Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. Refer to link:https://access.redhat.com/articles/7115356[OpenShift Jenkins Support Matrix] for more information. | |
| However, for Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. For more information, see link:https://access.redhat.com/articles/7115356[Support Matrix for OpenShift Jenkins releases]. |
|
|
||
| However, for OpenShift Extended Update Support (EUS) releases, only the `amd64` architecture is officially supported. As a result, OpenShift Jenkins images are shipped exclusively for `amd64` on these releases. This is because the {product-title} platform itself supports only the `amd64` architecture for EUS releases. Refer to link:https://access.redhat.com/articles/7115356[OpenShift Jenkins Support Matrix] for more information. | ||
|
|
||
| .When Red Hat updates Jenkins container images, are they available for all OpenShift versions simultaneously? |
There was a problem hiding this comment.
Suggested change
| .When Red Hat updates Jenkins container images, are they available for all OpenShift versions simultaneously? | |
| .When Red{nbsp}Hat updates Jenkins container images, are they available for all {product-title} versions simultaneously? |
|
|
||
| .How long are the released Jenkins images supported? | ||
|
|
||
| Red Hat supports only the latest Long-Term Support (LTS) version of the Jenkins core, as provided in our latest container images. We do not support multiple core versions. Our policy is to align with the latest Jenkins LTS version released by the upstream community. |
There was a problem hiding this comment.
Suggested change
| Red Hat supports only the latest Long-Term Support (LTS) version of the Jenkins core, as provided in our latest container images. We do not support multiple core versions. Our policy is to align with the latest Jenkins LTS version released by the upstream community. | |
| Red{nbsp}Hat supports only the latest Long-Term Support (LTS) version of the Jenkins core, as provided in our latest container images. We do not support multiple core versions. Our policy is to align with the latest Jenkins LTS version released by the upstream community. |
|
|
||
| Jenkins is no longer part of the {product-title} core payload. Releases are managed separately. However, our intent is to publish updated OpenShift Jenkins images for newly released {product-title} releases within a few weeks of the {product-title} GA release. | ||
|
|
||
| .Does Red Hat follow the upstream Jenkins lifecycle and LTS versions? |
There was a problem hiding this comment.
Suggested change
| .Does Red Hat follow the upstream Jenkins lifecycle and LTS versions? | |
| .Does Red{nbsp}Hat follow the upstream Jenkins lifecycle and LTS versions? |
|
|
||
| .Does Red Hat follow the upstream Jenkins lifecycle and LTS versions? | ||
|
|
||
| Yes. We align with the Jenkins upstream lifecycle and follow the LTS version. Red Hat typically ships OpenShift Jenkins image updates quarterly unless a critical fix requires an out-of-cycle release. |
There was a problem hiding this comment.
Suggested change
| Yes. We align with the Jenkins upstream lifecycle and follow the LTS version. Red Hat typically ships OpenShift Jenkins image updates quarterly unless a critical fix requires an out-of-cycle release. | |
| Yes. We align with the Jenkins upstream lifecycle and follow the LTS version. Red{nbsp}Hat typically ships OpenShift Jenkins image updates quarterly unless a critical fix requires an out-of-cycle release. |
| Yes. We align with the Jenkins upstream lifecycle and follow the LTS version. Red Hat typically ships OpenShift Jenkins image updates quarterly unless a critical fix requires an out-of-cycle release. | ||
|
|
||
| To verify the current Jenkins LTS version: | ||
| - Navigate to the Jenkins Catalog → Packages section |
There was a problem hiding this comment.
Suggested change
| - Navigate to the Jenkins Catalog → Packages section | |
| - Navigate to the Jenkins Catalog -> Packages section |
| To verify the current Jenkins LTS version: | ||
| - Navigate to the Jenkins Catalog → Packages section | ||
| - Search for “Jenkins” | ||
| - The result will show two packages—one of which is the Jenkins LTS package. |
There was a problem hiding this comment.
Suggested change
| - The result will show two packages—one of which is the Jenkins LTS package. | |
| - The result will show two packages, one of which is the Jenkins LTS package. |
per https://www.ibm.com/docs/en/ibm-style?topic=punctuation-dashes#em-dashes
|
|
||
| .Does the Jenkins release align with OpenShift versions? | ||
|
|
||
| Yes. Our goal is to maintain platform alignment—meaning Jenkins controller and agent images are built and tested for each supported {product-title} releases. |
There was a problem hiding this comment.
Suggested change
| Yes. Our goal is to maintain platform alignment—meaning Jenkins controller and agent images are built and tested for each supported {product-title} releases. | |
| Yes. Our goal is to maintain platform alignment. This means that Jenkins controller and agent images are built and tested for each supported {product-title} releases. |
openshift-ci
bot
removed
merge-review-in-progress
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Version(s):
Issue:
Link to docs preview:
QE review:
Additional information: