Version 2.0.1 incorrectly resolves required versions in dependencies
See original GitHub issueLooks like there is a regression after switching to “download latest by default” in 2.0.0
2020-09-17 11:49:21
Step 4/4 : RUN java -jar /app/bin/jenkins-plugin-manager.jar --war /app/jenkins/jenkins.war --plugins docker-workflow:1.22 workflow-durable-task-step:2.35
2020-09-17 11:49:21
2020-09-17 11:49:21
---> Running in 90ef99b3c292
2020-09-17 11:49:22
Unable to open /app/jenkins/jenkins.war
2020-09-17 11:49:22
Unable to get version from war file
2020-09-17 11:49:26
War not found, installing all plugins: /app/jenkins/jenkins.war
2020-09-17 11:49:26
Plugin docker-workflow:1.22 depends on workflow-durable-task-step:2.36, but there is an older version defined on the top level - workflow-durable-task-step:2.35
At the same time, even the most recent release of Docker Pipeline plugin requires 2.35:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:9 (5 by maintainers)
Top Results From Across the Web
Flutter pubspec dependency conflict - dart - Stack Overflow
I've a wired problem with resolving dependencies ...
Read more >Troubleshoot dependency version conflicts - Azure
In this article. Diagnose version mismatch issues; Mitigate version mismatch issues; Understand compatible dependency versions; Next steps.
Read more >How to identify and resolve a dependency conflict
Whenever the application is built, it will select the latest versions of unpinned packages, and those versions may introduce new, incompatible, requirements of ......
Read more >Resolving package version conflicts in Dart - iiro.dev
The fastest way to resolve this problem is to set the versions of both of the conflicting dependencies to any . Hold on...
Read more >Failed to resolve module org.mule ... - MuleSoft Help Center
Failed to resolve module org.mule.modules:mule-module-apikit-odata:2.0.1 (hover for more details or open this problem's Properties). Resolving dependency ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Jenkinsfile Runner is not really “messing” with it. Taking the packaging, there is just no Jenkins WAR which could be really used to retrieve the version as documented here: https://github.com/jenkinsci/plugin-installation-manager-tool/blob/master/plugin-management-library/src/main/java/io/jenkins/tools/pluginmanager/impl/PluginManager.java#L1064-L1072 . An alternative solution is needed, and it is going to be a problem with recent plugin releases requiring new core versions. I will create a patch
Yeah it’s a bit of a pain, possibly the error should be relaxed if there’s a compatible version declared elsewhere in the file.
We’ve been working around it by using the available-updates flag to update our file for us when that happens