[JIRA] (JENKINS-56858) unable to load plugins

[ykuo@mvista.com (JIRA)]

Yufen Kuo created an issue

Jenkins / JENKINS-56858 unable to load plugins Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-04-02 22:46 Environment: jenkins version <version>2.164.1</version> Priority: Major Reporter: Yufen Kuo followed the steps from https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md git clone https://github.com/jenkinsci/jenkinsfile-runner.git run the mvn package command cd /local/test/jenkins  wget http://mirrors.jenkins.io/war-stable/latest/jenkins.war unzip jenkins.war -d /local/test/jenkins/jenkins_home export JENKINS_HOME=/local/test/jenkins/jenkins_home run java -jar jenkins.war to install  suggested plugins create Jenkinsfile /local/test/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -w /local/test/jenkins -p /local/test/jenkins/jenkins_home/plugins -f /local/test/jenkins/foo -a "param1=Test&param2=MyTest"{{}} {{}} Then you will get messages like below, although my jenkins version is 2.164.1 and not 2.89. 1.436 [id=55] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.19 failed to load. {{ - You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.}} {{ at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)}} {{ at hudson.PluginManager$2$1$1.run(PluginManager.java:513)}} {{ at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)}} {{ at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)}} {{ at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065)}} {{ at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)}} {{ at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)}} {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} {{ at java.lang.Thread.run(Thread.java:748)}} {{ 1.439 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api)}} java.io.IOException: Pipeline: API v2.33 failed to load.{} Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[ykuo@mvista.com (JIRA)]

Yufen Kuo updated an issue

Jenkins / JENKINS-56858 unable to load plugins

Change By: Yufen Kuo Attachment: out

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo updated an issue

Jenkins / JENKINS-56858 unable to load plugins Change By: Yufen Kuo

followed the steps from [https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md] # git clone [https://github.com/jenkinsci/jenkinsfile-runner.git] # run the mvn package command # cd /local/test/jenkins #  {{wget [http://mirrors.jenkins.io/war-stable/latest/jenkins.war]}} # {{unzip jenkins.war -d /local/test/jenkins/jenkins_home}} # {{export JENKINS_HOME=/local/test/jenkins/jenkins_home}} # {{ {{ run java -jar jenkins.war to install  suggested plugins}} }} # create Jenkinsfile # /local/test/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -w /local/test/jenkins -p /local/test/jenkins/jenkins_home/plugins -f /local/test/jenkins/foo -a "param1=Test&param2=MyTest" {{}} {{}} Then you will get messages like below, although my jenkins version is 2.164.1 and not 2.89. see the attached out file for the complete output {{1.436 [id=55] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api)}}

{{java.io.IOException: Pipeline: Step API v2.19 failed to load.}}

\ {{ - You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.}} \ {{ at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626)}} \ {{ at hudson.PluginManager$2$1$1.run(PluginManager.java:513)}} \ {{ at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)}} \ {{ at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)}} \ {{ at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065)}} \ {{ at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)}} \ {{ at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)}} \ {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)}} \ {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)}} \

{{ at java.lang.Thread.run(Thread.java:748)}}

{{ 1.439 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api)}}

{{java.io.IOException: Pipeline: API v2.33 failed to load.{ { }}} }

Add Comment

[ykuo@mvista.com (JIRA)]

[bmathus+ossjira@cloudbees.com (JIRA)]

Baptiste Mathus assigned an issue to Evaristo Gutierrez

Jenkins / JENKINS-56858 unable to load plugins

Change By: Baptiste Mathus Assignee: Evaristo Gutierrez

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez updated an issue

Jenkins / JENKINS-56858 unable to load plugins

Change By: Evaristo Gutierrez Labels: triaged

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins Hi Yufen Kuo, thanks for using Jenkinsfile Runner! I see you have used "-w /local/test/jenkins" while you unzipped the WAR file in "/local/test/jenkins/jenkins_home". Could you please unzip the WAR in the first one and see whats is the result after that? Thanks!

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

Unzipping the war file into <directory> and set -w <directory> works. But setting -w option to directory contains war file does not work, setting -w option to full path to war file does not work either. setting -v 2.164.1  instead of -w option fails too. Running pipeline on jenkins 2.164.1 1.405 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api)

java.io.IOException: Pipeline: Step API v2.19 failed to load.

You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.

at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:513)

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

Setting -w <directory> where <directory> is there the WAR was unzipped is the way to go. If you do that, then you get the error you just provided?

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

the help text says: v (-version) VAL : jenkins version to use. Defaults to latest LTS. w (-jenkins-war) FILE : path to jenkins.war or exploded jenkins war directory   So it seems if you use -w option and pass path to jenkins.war, it would not work. Using -v option does not work either Both seems to be bugs to me, or help text needs to be updated.

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

Yufen Kuo I have reviewed and you are right, the help text is not appropriate. I have raised https://github.com/jenkinsci/jenkinsfile-runner/pull/104 to fix it.   Now that we've understood that, if you specify the exploded directory with the 2.164.1 version extracted, which is the behaviour?

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

If I specify the exploded directory with the -w option, it works.   But if I just specify the -v option (without -w option), I get the same error message.

Running pipeline on jenkins 2.164.1 1.405 [id=50] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.19 failed to load. You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin. at

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

Yufen Kuo could you please check if you can see these messages in the logs?

"Running pipeline on jenkins 2.164.1"

"Downloading jenkins 2.164.1" Thanks!

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

Yes, I do see the messages when running jenkinsfile-runner with -v option $ /usr/local/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -v 2.164.1 -p /var/jenkins_home/plugins -f /var/jenkins_home/foo -a param1=Test -a param2=MyTest

Running pipeline on jenkins 2.164.1

Downloading jenkins 2.164.1... 1.792 [id=32] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: Step API v2.19 (workflow-step-api)

java.io.IOException: Pipeline: Step API v2.19 failed to load.

You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.

at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:626) at hudson.PluginManager$2$1$1.run(PluginManager.java:513)

at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1065) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)

1.794 [id=52] SEVERE jenkins.InitReactorRunner$1#onTaskFailed: Failed Loading plugin Pipeline: API v2.33 (workflow-api) java.io.IOException: Pipeline: API v2.33 failed to load.

You must update Jenkins from v2.89 to v2.121.1 or later to run this plugin.

Pipeline: Step API v2.19 failed to load. Fix this plugin first.

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

Yufen Kuo the issue is that Jenkinsfile Runner expect the WAR to be already extracted (that's why warDir needs to be a directory and not the WAR file) but specifying the version only downloads the WAR, without extracting it. Oleg Nenashev do you have context on why it was made like that? Yufen Kuo if you use -Djenkins.version=2.164.1 in the mvn command, instead of using the -v option, it should work.

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

$ /usr/local/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -Djenkins.version=2.164.1 -p /var/jenkins_home/plugins -f /var/jenkins_home/foo "-Djenkins.version=2.164.1" is not a valid option

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

No, not at execution time but at building time: mvn package -Djenkins.version=2.164.1  /usr/local/git/jenkinsfile-runner/app/target/appassembler/bin/jenkinsfile-runner -p /var/jenkins_home/plugins -f /var/jenkins_home/foo

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo updated an issue

Jenkins / JENKINS-56858 unable to load plugins

Change By: Yufen Kuo Attachment: mvn_build.log

Add Comment

[ykuo@mvista.com (JIRA)]

Yufen Kuo commented on JENKINS-56858

Re: unable to load plugins

running mvn package -Djenkins.version=2.164.1 failed to build with error messages  below. I have attached the complete output in mvn_build.log. running mvn package without the -Djenkins.version builds successfully. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (display-info) on project setup: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-enforcer-plugin:3.0.0-M1:enforce (display-info) on project setup: Some Enforcer rules have failed. Look above for specific messages explaining why the rule failed.

Add Comment

[egutierrez@cloudbees.com (JIRA)]

Evaristo Gutierrez commented on JENKINS-56858

Re: unable to load plugins

Yufen Kuo I have reproduced and you are right, it's a matter of dependencies. If using the extracted WAR works for you, I'd recommend you to go through such option.

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev resolved as Not A Defect

Closing as Not a Defect after the review. Newer versions of Jenkinsfile Runner check core and plugin requirements, so it should not be a UX problem anymore

Jenkins / JENKINS-56858 unable to load plugins

Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)