Failed Loading plugin after an update of the CI service
How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!
While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.
Legacy Article
You are viewing an article from our legacy "FastTrack"
publication program, made available for informational purposes. Articles
in this program were published without a requirement for independent
editing or verification and are provided"as is" without
guarantee.
Before using any information from this article, independently verify its
suitability for your situation and project.
Issue
- After updating the CI service in Liferay Cloud you find some errors in the CI's log related with different plugins's load, the errors are similar to this one:
May 26, 2021 3:37:21 PM jenkins.InitReactorRunner$1 onTaskFailed
SEVERE: Failed Loading plugin DXP Cloud Builder v1.0-SNAPSHOT (private-05/11/2021 19:00-root) (dxp-cloud-builder)
java.io.IOException: Failed to load: DXP Cloud Builder (1.0-SNAPSHOT (private-05/11/2021 19:00-root))
- Update required: Matrix Authorization Strategy Plugin (2.6.5) to be updated to 2.6.6 or higher
- Update required: JUnit Plugin (1.29) to be updated to 1.48 or higher
at hudson.PluginWrapper.resolvePluginDependencies(PluginWrapper.java:950)
at hudson.PluginManager$2$1$1.run(PluginManager.java:550)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
at jenkins.model.Jenkins$5.runTask(Jenkins.java:1131)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:68)
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)
Environment
- Liferay Cloud infra environments after an update
Resolution
-
This happens for plugins which Jenkins considers to have been manually updated.
-
If that's the case, you should be able to resolve it by setting the environment variable PLUGINS_FORCE_UPGRADE to true and apply the changes (restart/redeploy the service), this action can be done in the DXP Cloud's web console, in the ci service's environment variables section, or using the
ci/LCP.json if you want to persist the information in the service's descriptor in the "env" section:
"env": {
"PLUGINS_FORCE_UPGRADE": "true",
[...]
},
Did this article resolve your issue ?