Uploaded image for project: 'Jenkins Website'
  1. Jenkins Website
  2. WEBSITE-634

Obtain changelog from GitHub releases

    Details

    • Type: New Feature
    • Status: In Progress (View Workflow)
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: content
    • Labels:
      None
    • Similar Issues:

      Description

      My local Jenkins alerts me regularly about new Jenkins releases and links to the Jenkins changelog at https://jenkins.io/changelog/. That changelog often does not contain the changes of the version announced (yet). Therefore I cannot take an informed decision about whether I need to upgrade or not.

       

      Example: The alert says 2.183 is available right now while I write this. The changelog only contains 2.182 and earlier. By tomorrow the changelog might be updated, so I will also defer my local upgrade at least until tomorrow.

        Attachments

          Issue Links

            Activity

            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            This is how it works at the moment unfortunately. The releases usually happen on Sundays, but we do not always prepare changelogs in advance. So there is a lag between a release and a changelog availability.

            If you need to make a decision without changelog, there is always a commit history. Changelogs are just a fine-tuned version of the pull requests we integrateover the week.

             

            CC Daniel Beck

             

            Show
            oleg_nenashev Oleg Nenashev added a comment - This is how it works at the moment unfortunately. The releases usually happen on Sundays, but we do not always prepare changelogs in advance. So there is a lag between a release and a changelog availability. If you need to make a decision without changelog, there is always a commit history. Changelogs are just a fine-tuned version of the pull requests we integrateover the week.   CC Daniel Beck  
            Hide
            danielbeck Daniel Beck added a comment - - edited

            If you want a changelog on the weekend, you'll need to write it yourself. I've done this for way too many years, now someone else gets to sacrifice their weekends and days off for no reason.

            To elaborate: While it's possible for anyone to prepare the weekly changelog (except merge the PR, but there are people who do that), with very few exceptions, it's been exclusively written by Oleg or me for the past four years or so. Nobody else bothers.

            Which means that when we're out on Sunday, and otherwise busy (or off) on Monday, there's not going to be changelog on Monday.

            Show
            danielbeck Daniel Beck added a comment - - edited If you want a changelog on the weekend, you'll need to write it yourself. I've done this for way too many years, now someone else gets to sacrifice their weekends and days off for no reason. To elaborate: While it's possible for anyone to prepare the weekly changelog (except merge the PR, but there are people who do that), with very few exceptions, it's been exclusively written by Oleg or me for the past four years or so. Nobody else bothers. Which means that when we're out on Sunday, and otherwise busy (or off) on Monday, there's not going to be changelog on Monday.
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I will take it and implement a way for Automated Changelog draft generation with help of Release Drafter

             

            Show
            oleg_nenashev Oleg Nenashev added a comment - I will take it and implement a way for Automated Changelog draft generation with help of Release Drafter  
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            I have created https://github.com/jenkinsci/jenkins/pull/4097 to automate generation of changelog drafts in GitHub releases.

             

            Once merged, we will need to update https://jenkins.io/changelog/ to reference GitHub releases for incoming (and delayed) weeklies

            Show
            oleg_nenashev Oleg Nenashev added a comment - I have created  https://github.com/jenkinsci/jenkins/pull/4097  to automate generation of changelog drafts in GitHub releases.   Once merged, we will need to update  https://jenkins.io/changelog/  to reference GitHub releases for incoming (and delayed) weeklies
            Hide
            danielbeck Daniel Beck added a comment -

            Timing wise would prefer a POC of that before introducing this change to jenkinsci/jenkins (and one that could handle data format errors since we're now separating changelog changes from site builds).

            Show
            danielbeck Daniel Beck added a comment - Timing wise would prefer a POC of that before introducing this change to jenkinsci/jenkins (and one that could handle data format errors since we're now separating changelog changes from site builds).
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Daniel Beck I think we can just stay in the transient state for a while when We generate changelogs with Release Drafter but then cop-edit them and put them manually to the Web site

            In parallel we can work on the PoC which would retrieve the data from GitHub

             

            Show
            oleg_nenashev Oleg Nenashev added a comment - Daniel Beck  I think we can just stay in the transient state for a while when We generate changelogs with Release Drafter but then cop-edit them and put them manually to the Web site In parallel we can work on the PoC which would retrieve the data from GitHub  

              People

              • Assignee:
                oleg_nenashev Oleg Nenashev
                Reporter:
                bananeweizen Michael Keppler
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: