New BOM version 807.v6d348e44c987 seems out of step with the versioning pattern

17 views
Skip to first unread message

Chris Kilding

unread,
May 6, 2021, 6:59:59 AM5/6/21
to jenkin...@googlegroups.com
Hi all,

The new BOM version today is 807.v6d348e44c987. This seems quite out of step with the previous versioning pattern - 27, 28, 29 etc. Was this change intentional?

Chris

Tim Jacomb

unread,
May 6, 2021, 9:56:32 AM5/6/21
to chris+...@chriskilding.com, Jenkins Developers

--
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/ba3ba5dd-6275-4273-ab21-d1828abdd337%40www.fastmail.com.

Chris Kilding

unread,
May 6, 2021, 10:05:59 AM5/6/21
to jenkin...@googlegroups.com
Great, thanks for confirming that.

Chris

Ullrich Hafner

unread,
May 7, 2021, 5:21:28 AM5/7/21
to Jenkins Developers
That means the maven enforcer will strike back unless all plugins use CD ;-) The frequency of required updates will be an magnitude higher now… 

Tim Jacomb

unread,
May 7, 2021, 6:12:43 AM5/7/21
to Jenkins Developers
> That means the maven enforcer will strike back unless all plugins use CD ;-) The frequency of required updates will be an magnitude higher now… 

While bom does use the CD mechanism for release it doesn't actually do 'CD'

The releases are triggered either manually or if someone merges a PR with an 'interesting label' like the 'enhancement' label

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/C9A32AE4-F08B-4806-BC0D-3FC7ACE829D6%40gmail.com.

Jesse Glick

unread,
May 7, 2021, 8:56:35 AM5/7/21
to Jenkins Dev
On Fri, May 7, 2021 at 6:12 AM Tim Jacomb <timja...@gmail.com> wrote:
The releases are triggered either manually or if someone merges a PR with an 'interesting label'

Reply all
Reply to author
Forward
0 new messages