Hi all, recently Jenkins introduced a BOM for managing versions of libraries it ships with so that plugins can pick up a consistent set. ( https://github.com/jenkinsci/jenkins/pull/4150 , https://github.com/jenkinsci/plugin-pom/pull/229)
When the plugin changes are merged I would like to be able to use the BOM for older historic versions of Jenkins (for example the current LTS or older). In order to do that I would need to be able to deploy to https://repo.jenkins-ci.org/releases/org/jenkins-ci/main/jenkins-bom/ Whilst I can make a PR to the repo-permission updater and create/reverse engineer the bom for some specific versions would this be ok with people (as I understand it is not possible to restrict to publishing specific versions)? Given the source is only a BOM and that would be in the repository anyway do others see a need to tag these in source control somewhere? Regards /James -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/011e9c5c-51ae-4a6b-bed5-ca9f74129ed4%40googlegroups.com.
