Details

    • Similar Issues:

      Description

      followed the steps from https://github.com/jenkinsci/jenkinsfile-runner/blob/master/README.md

      1. git clone https://github.com/jenkinsci/jenkinsfile-runner.git
      2. run the mvn package command
      3. cd /local/test/jenkins
      4.  wget http://mirrors.jenkins.io/war-stable/latest/jenkins.war
      5. unzip jenkins.war -d /local/test/jenkins/jenkins_home
      6. export JENKINS_HOME=/local/test/jenkins/jenkins_home
      7. {{run java -jar jenkins.war to install  suggested plugins}}
      8. create Jenkinsfile
      9. /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.

        Attachments

        1. mvn_build.log
          2.28 MB
        2. out
          106 kB

          Activity

          Hide
          egutierrez Evaristo Gutierrez added a comment -

          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.

          Show
          egutierrez Evaristo Gutierrez added a comment - 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.
          Hide
          ykuo Yufen Kuo added a comment -

          $ /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

          Show
          ykuo Yufen Kuo added a comment - $ /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
          Hide
          egutierrez Evaristo Gutierrez added a comment -

          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

           

          Show
          egutierrez Evaristo Gutierrez added a comment - 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  
          Hide
          ykuo Yufen Kuo added a comment -

          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.

           

          Show
          ykuo Yufen Kuo added a comment - 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.  
          Hide
          egutierrez Evaristo Gutierrez added a comment -

          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.

          Show
          egutierrez Evaristo Gutierrez added a comment - 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.

            People

            • Assignee:
              egutierrez Evaristo Gutierrez
              Reporter:
              ykuo Yufen Kuo
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: