search

jenkinsci / custom-war-packager

Custom Jenkins WAR packager for Jenkins
https://jenkins.io/blog/2018/10/16/custom-war-packager/
MIT License
86 stars 69 forks source link

Add support for Jenkins Plugin BOM as a source of plugin versions when using YAML plugin list #165

Open oleg-nenashev opened 4 years ago

oleg-nenashev commented 4 years ago

Jenkins Plugin Bill of Materials provides a list of plugins which are cross-verified to some extent: https://github.com/jenkinsci/bom . When using pom.xml as a plugin list input, it is possible to use BOM via Maven features. But it is not possible for a YAML configuration. It would be awesome to support it so that users can delegate version management of some components they bundle

oleg-nenashev commented 4 years ago

CC @alxsap @LinuxSuRen @sladyn98 who might have some feedback about usefullness of such option

LinuxSuRen commented 4 years ago

I know CWP already supported using a pom.xml as the plugin list. But I didn't use it too much. So I believe that adding support for Jenkins BOM as a source of plugin versions is great. It's always kill me when handling the version conflicts.

oleg-nenashev commented 4 years ago

It's always kill me when handling the version conflicts.

This is exactly why I submitted it. Trying to update Jenkinsfile Runner demos and the build flow 😢

alxsap commented 4 years ago

We are using a simple list of plugins we need and a custom script generates the list of the latest plugins and their transitive dependencies. The script automatically updates the packager-config.yml.

Therefore currently we don't have this requirement. But there have been reasons, why we implemented this script - we had exactly those issues. 😉

oleg-nenashev commented 4 years ago

I consider doing a new Maven-based packaging flow which would allow to easily consume BOMs and manage dependencies. https://github.com/jenkinsci/jenkinsfile-runner/issues/344