[
https://issues.apache.org/jira/browse/HIVE-28339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859862#comment-17859862
]
Stamatis Zampetakis commented on HIVE-28339:
--------------------------------------------
Here is a rough outline of the steps that I have in mind.
# Build a new Jenkins image using the aforementioned Dockerfile
# Push the image to some container registry:
## [https://hub.docker.com/r/kgyrtkirk/htk-jenkins]
## [https://hub.docker.com/r/apache/hive-ci-jenkins/] (Need to request a new
Docker namespace from INFRA)
## [https://hub.docker.com/r/zabetak/hive-ci-jenkins/]
# Take backups from existing Jenkins instance
# Test/Start new Jenkins image locally (and ensure backups are working if
necessary)
# Send an email to dev@ about estimated downtime
# Modify the kubernetes deployment file to point to new image (if necessary)
# Restart the Jenkins pod (with or without backups) and hope for the best
# Send an email when CI is operational
Please add/remove/suggest others as you see fit.
> Upgrade Jenkins version in CI from 2.332.3 to 2.452.2
> -----------------------------------------------------
>
> Key: HIVE-28339
> URL: https://issues.apache.org/jira/browse/HIVE-28339
> Project: Hive
> Issue Type: Task
> Reporter: Stamatis Zampetakis
> Priority: Major
>
> The Jenkins version that is used in [https://ci.hive.apache.org/] is
> currently at [2.332.3|https://www.jenkins.io/changelog-stable/#v2.332.3]
> which was released in 2022.
> The latest stable version at the moment is
> [2.452.2|https://www.jenkins.io/changelog-stable/#v2.452.2] and contains many
> improvements, bug and CVE fixes.
> The Dockerfile that is used to build the Jenkins file can be found here:
> [https://github.com/kgyrtkirk/hive-test-kube/blob/master/htk-jenkins/Dockerfile]
> The Kubernetes deployment files can be found here:
> [https://github.com/kgyrtkirk/hive-test-kube/tree/master/k8s]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
