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

1 view
Skip to first unread message

jglick@cloudbees.com (JIRA)

unread,
Mar 6, 2018, 11:38:01 AM3/6/18
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / New Feature JENKINS-48578
Create BOM for components included into the Core
Change By: Jesse Glick
Labels: essentials
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

milkiwaysabe@gmail.com (JIRA)

unread,
Jun 21, 2018, 8:35:02 PM6/21/18
to jenkinsc...@googlegroups.com
jang hyemi updated an issue
Change By: jang hyemi
Sprint: Essentials - Milestone 2

tyler@monkeypox.org (JIRA)

unread,
Aug 23, 2018, 11:17:03 AM8/23/18
to jenkinsc...@googlegroups.com
R. Tyler Croy updated an issue

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
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

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

unread,
Dec 25, 2018, 4:55:03 AM12/25/18
to jenkinsc...@googlegroups.com
Oleg Nenashev assigned an issue to Unassigned
Change By: Oleg Nenashev
Assignee: Oleg Nenashev
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

jglick@cloudbees.com (JIRA)

unread,
May 30, 2019, 12:47:03 PM5/30/19
to jenkinsc...@googlegroups.com
Jesse Glick commented on New Feature 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.

jglick@cloudbees.com (JIRA)

unread,
Jul 9, 2019, 1:02:07 PM7/9/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
Change By: Jesse Glick
Component/s: bom
Component/s: core

jglick@cloudbees.com (JIRA)

unread,
Jul 24, 2019, 12:54:03 PM7/24/19
to jenkinsc...@googlegroups.com
 
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.

jnord@cloudbees.com (JIRA)

unread,
Aug 13, 2019, 1:27:02 PM8/13/19
to jenkinsc...@googlegroups.com
James Nord started work on New Feature JENKINS-48578
 
Change By: James Nord
Status: Reopened In Progress

jnord@cloudbees.com (JIRA)

unread,
Aug 13, 2019, 1:27:02 PM8/13/19
to jenkinsc...@googlegroups.com

jnord@cloudbees.com (JIRA)

unread,
Aug 13, 2019, 1:28:01 PM8/13/19
to jenkinsc...@googlegroups.com
James Nord commented on New Feature 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...)

mwynnmackenzie@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 11:09:03 AM9/18/19
to jenkinsc...@googlegroups.com
Mark Wynn-Mackenzie updated an issue
 
Change By: Mark Wynn-Mackenzie
Labels: lts-cand
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

mwynnmackenzie@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 11:09:04 AM9/18/19
to jenkinsc...@googlegroups.com

mwynnmackenzie@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 11:11:02 AM9/18/19
to jenkinsc...@googlegroups.com

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

unread,
Sep 18, 2019, 11:39:03 AM9/18/19
to jenkinsc...@googlegroups.com

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

unread,
Sep 18, 2019, 11:39:04 AM9/18/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on New Feature 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

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

unread,
Sep 18, 2019, 11:39:04 AM9/18/19
to jenkinsc...@googlegroups.com

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 11:58:03 AM9/18/19
to jenkinsc...@googlegroups.com
James Nord updated an issue
Change By: James Nord
Labels: lts-candidate

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 12:04:04 PM9/18/19
to jenkinsc...@googlegroups.com

>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.

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 12:05:02 PM9/18/19
to jenkinsc...@googlegroups.com
James Nord edited a comment on New Feature JENKINS-48578
>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.

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 12:07:02 PM9/18/19
to jenkinsc...@googlegroups.com

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

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 12:08:03 PM9/18/19
to jenkinsc...@googlegroups.com
James Nord assigned an issue to Mark Wynn-Mackenzie
 
Change By: James Nord
Assignee: James Nord Mark Wynn-Mackenzie

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

unread,
Sep 18, 2019, 12:09:02 PM9/18/19
to jenkinsc...@googlegroups.com
Oleg Nenashev commented on New Feature 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

 

jnord@cloudbees.com (JIRA)

unread,
Sep 18, 2019, 12:25:02 PM9/18/19
to jenkinsc...@googlegroups.com

>  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.

dbeck@cloudbees.com (JIRA)

unread,
Mar 11, 2020, 2:53:04 AM3/11/20
to jenkinsc...@googlegroups.com

Why is this issue still open?

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

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

unread,
Mar 11, 2020, 3:42:02 AM3/11/20
to jenkinsc...@googlegroups.com
Oleg Nenashev resolved as Fixed
 

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

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

mwynnmackenzie@cloudbees.com (JIRA)

unread,
Mar 11, 2020, 5:21:03 AM3/11/20
to jenkinsc...@googlegroups.com
Mark Wynn-Mackenzie commented on New Feature JENKINS-48578
 
Re: Create BOM for components included into the Core

Yes, they are. Sorry, it just got missed.

dbeck@cloudbees.com (JIRA)

unread,
Apr 1, 2020, 3:40:03 PM4/1/20
to jenkinsc...@googlegroups.com

dbeck@cloudbees.com (JIRA)

unread,
Apr 1, 2020, 3:42:04 PM4/1/20
to jenkinsc...@googlegroups.com
Daniel Beck commented on New Feature 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

Reply all
Reply to author
Forward
0 new messages