[JIRA] (JENKINS-56013) Jenkins LTS shows prerelease plugins

1 view
Skip to first unread message

michael.kriese@visualon.de (JIRA)

unread,
Feb 7, 2019, 12:43:03 AM2/7/19
to jenkinsc...@googlegroups.com
Michael Kriese created an issue
 
Jenkins / Bug JENKINS-56013
Jenkins LTS shows prerelease plugins
Issue Type: Bug Bug
Assignee: Unassigned
Components: core
Created: 2019-02-07 05:42
Environment: Jenkins ver. 2.150.2
http://updates.jenkins-ci.org/update-center.json
Priority: Critical Critical
Reporter: Michael Kriese

The update center is showing the following plugins with a prerelease version

I think there should no prerelease be visible. At least for the Jenkins LTS release.

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

michael.kriese@visualon.de (JIRA)

unread,
Feb 7, 2019, 12:46:02 AM2/7/19
to jenkinsc...@googlegroups.com
Michael Kriese updated an issue
Change By: Michael Kriese
Component/s: git-client-plugin
Component/s: git-plugin

dbeck@cloudbees.com (JIRA)

unread,
Feb 7, 2019, 4:16:02 AM2/7/19
to jenkinsc...@googlegroups.com
Daniel Beck updated an issue
Change By: Daniel Beck
Component/s: core

dbeck@cloudbees.com (JIRA)

unread,
Feb 7, 2019, 4:17:04 AM2/7/19
to jenkinsc...@googlegroups.com
Daniel Beck commented on Bug JENKINS-56013
 
Re: Jenkins LTS shows prerelease plugins

This is not a core bug, or an infra bug. We only support "alpha" and "beta" keywords in version numbers as documented on https://jenkins.io/doc/developer/publishing/releasing-experimental-updates/ and all other releases are eligible to be listed.

dbeck@cloudbees.com (JIRA)

unread,
Feb 7, 2019, 7:02:02 AM2/7/19
to jenkinsc...@googlegroups.com

michael.kriese@visualon.de (JIRA)

unread,
Feb 7, 2019, 7:40:01 AM2/7/19
to jenkinsc...@googlegroups.com

It would be a good idea to use semantic versioning to check for a prerelease. Or at lease check for a hyphen.

dbeck@cloudbees.com (JIRA)

unread,
Feb 7, 2019, 8:30:03 AM2/7/19
to jenkinsc...@googlegroups.com

If you want to work towards consensus with the plugin developers who regularly release versions containing hyphens, or worse, and expect these releases to be available, go for it.

 

michael.kriese@visualon.de (JIRA)

unread,
Feb 7, 2019, 9:19:02 AM2/7/19
to jenkinsc...@googlegroups.com

May the version string can be made more restrictive (semantic verion 2.0) in a future release (at least for jenkins plugins).
The developer docu should advice to use semantic version 2.0 compatible strings.

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 11, 2019, 4:31:02 PM2/11/19
to jenkinsc...@googlegroups.com
Mark Waite updated Bug JENKINS-56013
 

Fixed by removing the poorly chosen version names from the Jenkins update center and by reminding me (the plugin maintainer) that I should read documentation more carefully before choosing a version string.

Broader changes to the update center should not be assigned to the git client plugin or git plugin components.

If you'd like to use this bug report for a larger proposal to apply semantic versioning in the update center, that is possible, though a Jenkins Enhancement Proposal (JEP) is probably a better choice for that broad discussion.

Change By: Mark Waite
Status: Open Fixed but Unreleased
Resolution: Fixed

mark.earl.waite@gmail.com (JIRA)

unread,
Feb 11, 2019, 4:31:02 PM2/11/19
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Fixed but Unreleased Resolved

mark.earl.waite@gmail.com (JIRA)

unread,
Oct 22, 2019, 9:32:50 PM10/22/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Fixed
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages