[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Stefan Verhoeff commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Sure that might solve MY issue right now. The point is that this issue exists for everyone who upgrades mq-notifier-plugin, so this is a bug that needs to fixed in the plugin itself and not with a workaround. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5431.1561117440129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Thien Vu commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Hi you can go to the link above. Change it to your plugin: mq-notifier-plugin try to get the older version and upload to Jenkins to match with workflow-step-api Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5429.1561117080372%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Stefan Verhoeff commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Thanks Thien Vu. I already have 2.14 installed, but because the new version of mq-notifier-plugin requires a newer version , it was installed an not compatible with the Jenkins version. My point of reporting this issue is to highlight that the update path is broken for older Jenkins versions. I guess the minimal required Jenkins version for mq-notifier-plugin can be updated to v2.121.1 to avoid this? At least a user can then not break Jenkins accidentally. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5418.1561116240175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Thien Vu commented on JENKINS-58120 Re: Fail to start on due to Pipeline: Step API dependency Hi, You can go to this link: https://updates.jenkins.io/download/plugins/workflow-step-api/ Download the v2.14 and upload into Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200165.1561046097000.5003.1561066860226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-58120) Fail to start on due to Pipeline: Step API dependency
Title: Message Title Stefan Verhoeff created an issue Jenkins / JENKINS-58120 Fail to start on due to Pipeline: Step API dependency Issue Type: Bug Assignee: Tomas Westling Components: mq-notifier-plugin Created: 2019-06-20 15:54 Environment: Jenkins ver. 2.89.3, mq-notifier-plugin 1.2.8 Priority: Minor Reporter: Stefan Verhoeff After upgrading the mq-notifier-plugin on 1.2.8 on Jenkins ver. 2.89.3, Jenkins failed to start up properly. It looks this Jenkins version breaks because of the "Pipeline: Step API" dependency which needs Jenkins version v2.121.1 or later. Startup error log: Jun 20, 2019 9:55:27 AM jenkins.InitReactorRunner$1 onTaskFailed SEVERE: Failed Loading plugin Pipeline: Step API v2.20 (workflow-step-api) java.io.IOException: Pipeline: Step API v2.20 failed to load. - You must update Jenkins from v2.89.3 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
