[ 
https://issues.apache.org/jira/browse/HIVE-28339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17861089#comment-17861089
 ] 

Stamatis Zampetakis commented on HIVE-28339:
--------------------------------------------

I tested starting Jenkins from a vanilla Jenkins image 
(jenkins/jenkins:lts-jdk17) using the jenkins_home_backup.tar obtained 
previously.

{noformat}
tar -xvf jenkins_home_backup.tar
docker run -p 35000:8080 -v 
/home/stamatis/Issues/HIVE-28339/var/jenkins_home:/var/jenkins_home 
jenkins/jenkins:lts-jdk17 
{noformat}

Unfortunately Jenkins cannot start and there are many SEVERE errors due to the 
plugins and configuration that is present in the jenkins_home directory.
{noformat}> docker logs CONTAINER_NAME 2>&1 | grep SEVERE
2024-07-01 08:04:00.498+0000 [id=32]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Mina SSHD API 
:: Core v2.12.1-101.v85b_e08b_780dd (mina-sshd-api-core)
2024-07-01 08:04:00.499+0000 [id=32]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin SSH server 
v3.322.v159e91f6a_550 (sshd)
2024-07-01 08:04:00.537+0000 [id=55]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Jenkins GIT 
server Plugin v1.11 (git-server)
2024-07-01 08:04:00.538+0000 [id=55]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: 
Deprecated Groovy Libraries v588.v576c103a_ff86 (workflow-cps-global-lib)
2024-07-01 08:04:00.539+0000 [id=55]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: 
Declarative v2.2064.v5eef7d0982b_e (pipeline-model-definition)
2024-07-01 08:04:00.540+0000 [id=55]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline 
implementation for Blue Ocean v1.25.5 (blueocean-pipeline-api-impl)
2024-07-01 08:04:00.541+0000 [id=55]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Bitbucket 
Pipeline for Blue Ocean v1.25.5 (blueocean-bitbucket-pipeline)
2024-07-01 08:04:00.542+0000 [id=38]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Events API for 
Blue Ocean v1.25.5 (blueocean-events)
2024-07-01 08:04:00.543+0000 [id=38]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Git Pipeline 
for Blue Ocean v1.25.5 (blueocean-git-pipeline)
2024-07-01 08:04:00.543+0000 [id=38]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin GitHub Pipeline 
for Blue Ocean v1.25.5 (blueocean-github-pipeline)
2024-07-01 08:04:00.545+0000 [id=33]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Blue Ocean 
Pipeline Editor v1.25.5 (blueocean-pipeline-editor)
2024-07-01 08:04:00.546+0000 [id=33]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Blue Ocean 
v1.25.5 (blueocean)
2024-07-01 08:04:00.603+0000 [id=45]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Docker Pipeline 
v1.28 (docker-workflow)
2024-07-01 08:04:00.704+0000 [id=45]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Matrix 
Authorization Strategy Plugin v3.2.2 (matrix-auth)
2024-07-01 08:04:04.340+0000 [id=46]    SEVERE  
jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading global config
2024-07-01 08:04:04.342+0000 [id=26]    SEVERE  
hudson.util.BootFailure#publish: Failed to initialize Jenkins
{noformat}

So I replying to [my own 
previous|https://issues.apache.org/jira/browse/HIVE-28339?focusedCommentId=17860168&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17860168]
 it is not possible to use a vanilla Jenkins image and we need to publish and 
maintain our custom Jenkins images with all the necessary plugins installed.

I managed to make Jenkins start by modifying slightly the respective 
[Dockerfile|https://github.com/kgyrtkirk/hive-test-kube/blob/master/htk-jenkins/Dockerfile]
 that we use currently in CI. I will raise an INFRA ticket to request  the 
https://hub.docker.com/r/apache/hive-ci-jenkins/ to be created so we can 
publish the image there. I will also create a PR for apache/hive with the 
Dockerfile so that we have everything in the official Apache namespace.

> 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
>            Assignee: 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)

Reply via email to