[JIRA] (JENKINS-48578) Create BOM for components included into the Core

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core Change By: Jesse Glick Labels: essentials Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[milkiwaysabe@gmail.com (JIRA)]

jang hyemi updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core

Change By: jang hyemi Sprint: Essentials - Milestone 2

Add Comment

[tyler@monkeypox.org (JIRA)]

R. Tyler Croy updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core

I'm not seeing how this is related to Jenkins Evergreen so I'm bouncing it out of our milestone Change By: R. Tyler Croy Labels: essentials Sprint: Evergreen - Milestone 2

Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev assigned an issue to Unassigned

Jenkins / JENKINS-48578 Create BOM for components included into the Core

Change By: Oleg Nenashev Assignee: Oleg Nenashev

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-48578

Re: Create BOM for components included into the Core A possible subtask: move symbol-annotation out of the structs-plugin repository, as it rarely changes and does not need the same lifecycle.

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: Jesse Glick Component/s: bom Component/s: core

Add Comment

[jglick@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-48578

Re: Create BOM for components included into the Core BOM for Jenkins core components like modules As of JENKINS-55582, there would not be any, at least in the stock Jenkins distribution.

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord started work on JENKINS-48578

Change By: James Nord Status: Reopened In Progress

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord assigned an issue to James Nord

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: James Nord Assignee: James Nord

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-48578

Re: Create BOM for components included into the Core Would selectivly need to publish a few BOMs for older lines so that the plugin-pom would still work (which would get funky as far as permissions in repository are perhaps concerned...)

Add Comment

[mwynnmackenzie@cloudbees.com (JIRA)]

Mark Wynn-Mackenzie updated an issue

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: Mark Wynn-Mackenzie Labels: lts-cand

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[mwynnmackenzie@cloudbees.com (JIRA)]

[mwynnmackenzie@cloudbees.com (JIRA)]

Mark Wynn-Mackenzie updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core

Change By: Mark Wynn-Mackenzie Labels: lts-candidate

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core

Change By: Oleg Nenashev Labels: lts-candidate

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-48578

Re: Create BOM for components included into the Core There is no way it gets backported to LTS, so I removed the label

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev updated an issue

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: Oleg Nenashev Component/s: core

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord updated an issue

Jenkins / JENKINS-48578 Create BOM for components included into the Core

Change By: James Nord Labels: lts-candidate

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-48578

Re: Create BOM for components included into the Core

>There is no way it gets backported to LTS, so I removed the label

yes there is, I can adapt it and it can be included.  the label is to start a discussion.  I do not think the libraries have changed here so it can also be a simple cherry-pick. Granted you could call this a feature that is not eligible, but you could call it a bug that the correct libraries are not used in a plugin build based on the Jenkins version.

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord edited a comment on JENKINS-48578

Re: Create BOM for components included into the Core

>There is no way it gets backported to LTS, so I removed the label yes there is, I can adapt it and it can be included.  the label is to start a discussion.  I do not think the libraries have changed here so it can also be a simple cherry-pick. Granted you could call this a feature that is not eligible, but you could call it a bug that the correct libraries are not used in a plugin build based on the Jenkins version.

There have also been some special cases historically.

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-48578

Re: Create BOM for components included into the Core

specifically we are talking about the BOM in core for backport not the plugin-pom. https://github.com/jenkinsci/jenkins/pull/4150

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord assigned an issue to Mark Wynn-Mackenzie

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: James Nord Assignee: James Nord Mark Wynn-Mackenzie

Add Comment

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev commented on JENKINS-48578

Re: Create BOM for components included into the Core Note that the 2.190.1 RC has testing has already started. Even if there is a consensus to backport it, it is likely to be 2.190.2 only   My suggestion would be to actually consider doing this:

> Would selectivly need to publish a few BOMs for older lines so that the plugin-pom would still work (which would get funky as far as permissions in repository are perhaps concerned...)

It is funky indeed, but it is technically doable. My suggestion would be to deploy BOMs for 2.138.3 and above so that we can start consuming it in plugins quickly. Deploying it for last baseline releases (2.138.3, 2.150.3, 2.164.3, 2.176.3/4) would be enough imho

Add Comment

[jnord@cloudbees.com (JIRA)]

James Nord commented on JENKINS-48578

Re: Create BOM for components included into the Core

>  Even if there is a consensus to backport it, it is likely to be 2.190.2 only If it prevents the "oh shit I forgot to push a release of the bom after a release was made" that's a win in my eyes.  We're aware the .1 boat has sailed and we where a little late to merge the original bom and hence make the backport request.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-48578

Re: Create BOM for components included into the Core

Why is this issue still open?

Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[o.v.nenashev@gmail.com (JIRA)]

Oleg Nenashev resolved as Fixed

I think all proposed changes are delivered. All minor follow-ups can be handled separately

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed

Add Comment

[mwynnmackenzie@cloudbees.com (JIRA)]

Mark Wynn-Mackenzie commented on JENKINS-48578

Re: Create BOM for components included into the Core Yes, they are. Sorry, it just got missed.

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck updated an issue

Jenkins / JENKINS-48578

Create BOM for components included into the Core

Change By: Daniel Beck Labels: lts-candidate

Add Comment

[dbeck@cloudbees.com (JIRA)]

Daniel Beck commented on JENKINS-48578

Re: Create BOM for components included into the Core James Nord If you label an issue lts-candidate, you should make sure its issue type doesn't disqualify it from backporting: https://issues.jenkins-ci.org/issues/?filter=12146

Add Comment