retrospecitvly publishing the jenkins bom

[James Nord]

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

[Daniel Beck]

Isn't this what https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/ is for?

> --
> 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 jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/011e9c5c-51ae-4a6b-bed5-ca9f74129ed4%40googlegroups.com.

[Jesse Glick]

On Mon, Oct 21, 2019 at 7:51 AM Daniel Beck <m...@beckweb.net> wrote:
> Isn't this what https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/ is for?

No, James is discussing the core BOM which defines things like
libraries that are dependencies of `jenkins-core`. `jenkinsci/bom` is
complementary but focused on managing dependencies for use from
plugins, especially dependencies on other plugins.

[James Nord]

So I shall take silence as create a PR and be damned :)

[Mark Waite]

I definitely like the idea of retroactively available core BOM's

--

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 jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1dd0ca9-f6dd-4110-979b-56972749522b%40googlegroups.com.

--

Thanks!

Mark Waite

[James Nord]

Created https://github.com/jenkins-infra/repository-permissions-updater/pull/1377 

On Wednesday, October 30, 2019 at 11:54:55 PM UTC, Mark Waite wrote:

I definitely like the idea of retroactively available core BOM's

On Wed, Oct 30, 2019 at 4:35 PM James Nord <jn...@cloudbees.com> wrote:

So I shall take silence as create a PR and be damned :)

On Monday, October 21, 2019 at 7:04:37 PM UTC+1, Jesse Glick wrote:

On Mon, Oct 21, 2019 at 7:51 AM Daniel Beck <m...@beckweb.net> wrote:
> Isn't this what https://repo.jenkins-ci.org/releases/io/jenkins/tools/bom/ is for?

No, James is discussing the core BOM which defines things like
libraries that are dependencies of `jenkins-core`. `jenkinsci/bom` is
complementary but focused on managing dependencies for use from
plugins, especially dependencies on other plugins.

--
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 jenkin...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a1dd0ca9-f6dd-4110-979b-56972749522b%40googlegroups.com.

--

Thanks!

Mark Waite

[Oleg Nenashev]

Fine with me.

Probably we should think about renaming components to "core-bom" and "plugin-bom" to stop creating confusion

[James Nord]

I'm not going to be working on this until the new year so if people think we do need to rename `org.jenkins-ci.main:jenkins-bom` to `org.jenkins-ci.main:core-bom` then hving a consensus by 6th janurary would be helpful,

I do not think the plugin-bom should actually have "bom" in its name given that it is not a bill of materials given nothing is every shipped with that set of components, thus if renaming just changing that to something non bom should remove the confusion. Happy holidays!

/James

[Oleg Nenashev]

 if people think we do need to rename `org.jenkins-ci.main:jenkins-bom` to `org.jenkins-ci.main:core-bom` then hving a consensus by 6th janurary would be helpful,

For me plugin BOM artifactId is more confusing. I do not mind it being called "BOM", but the name is definitely confusing. On the other hand, we could include Core BOM dependencies into the "BOM" definition, so it would be less of a concern for end users