How do release notes work?

[Stéphane BOBIN]

Hi friends!

I am trying to understand how release notes work for Jenkins plugins. 

On the GitHub repo side, I could see that I can click on the "Create a new release" link on the GitHub repo menu on the right. 

On the Jenkins plugin page, I could see that there is a "Release" link in the menu on the top. It leads to a similar list.

I randomly selected a Jenkins plugin (Pipeline Graph View) and I could see that both lists are not in sync:

• https://github.com/jenkinsci/pipeline-graph-view-plugin/releases: GitHub releases have always been with detailed logs and fancy icons since the beginning.
• https://plugins.jenkins.io/pipeline-graph-view/releases: Jenkins releases have been basic from the beginning to 489.* and changed to detailed logs and fancy icons since 491.* only.

How does it work? It does not seem automatic? Is there some doc about that?

Thanks!

Stéphane

[Winter, Markus]

Afaik, the release page on plugins.jenkins.io only loads the first page from github. So any release that is on the second page or higher in github only gets the basic info.

--
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 visit https://groups.google.com/d/msgid/jenkinsci-dev/d3a8d3c1-1261-483f-b0d4-7b48f97a5d0an%40googlegroups.com.

[Mark Waite]

On Tuesday, May 6, 2025 at 8:45:52 AM UTC-6 Stephane wrote:

 

I randomly selected a Jenkins plugin (Pipeline Graph View) and I could see that both lists are not in sync:

• https://github.com/jenkinsci/pipeline-graph-view-plugin/releases: GitHub releases have always been with detailed logs and fancy icons since the beginning.
• https://plugins.jenkins.io/pipeline-graph-view/releases: Jenkins releases have been basic from the beginning to 489.* and changed to detailed logs and fancy icons since 491.* only.

How does it work? It does not seem automatic? Is there some doc about that?

 The "Improve this page" link at the bottom of the plugins site links to the GitHub repository that implements the plugins site.  The plugins site is generated every 6 hours.  The plugins site collects documentation, release history, and usage data into a static site that is published as https://plugins.jenkins.io 

Mark Waite

[Zbynek Konecny]

Hi,

there are 2 components involved in this: a NodeJS app that fetches the changelogs from GitHub API and caches it locally

endpoint: https://plugin-site-issues.jenkins.io/api/plugin/pipeline-graph-view/releases
source code: https://github.com/jenkins-infra/docker-plugin-site-issues/blob/main/src/db.ts#L228

and the Plugin Site that gets information from said NodeJS app.
The Plugin Site is mostly static, but the changelogs are fetched from the client, that's why they load a bit later than the version numbers.
New versions of a plugin will appear on the Plugin Site within 6 hours of being published to the Update Center, and updates changelog for existing versions should be reflected after 1 hour (caching interval of the Node app).

Currently the Node app has a hard-coded limit of 10 releases. It should be possible to either increase the limit or implement pagination for this, if anyone's interested.

Cheers,
Zbynek

--

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 visit https://groups.google.com/d/msgid/jenkinsci-dev/e67d492d-2298-43c1-b092-193ac5b2a903n%40googlegroups.com.