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

Support publishing documentation for the last released version instead of the latest docs

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: plugin-site
    • Labels:
      None
    • Epic Link:
    • Similar Issues:

      Description

      Currently the Plugin Site displayes documentation for the master branch. This documentation may be different from what is available in the last release. It would be nice to support visualizing data for the last release.

       

      Open issues:

      • We need to map release versions to tags. There is no standard tagging policy for plugins
      • We need to ensure the plugin documentation is refreshed when a release happens

       

        Attachments

          Issue Links

          links to

          Web Link PR

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            zbynek Zbynek Konecny added a comment -

            Oleg Nenashev is there anything to do for this one once WEBSITE-648 works? Maintainer can then use $version Maven property as part of the github URL, meaning that each version will have a different docs URL, so the plugin site API cache will be forced to load the correct one. This works for any reasonable tagging system (no matter whether you use "plugin-1.2.3" or "v1.2.3", you can adjust the url in POM accordingly).

            Show
            zbynek Zbynek Konecny added a comment - Oleg Nenashev is there anything to do for this one once WEBSITE-648 works? Maintainer can then use $version Maven property as part of the github URL, meaning that each version will have a different docs URL, so the plugin site API cache will be forced to load the correct one. This works for any reasonable tagging system (no matter whether you use "plugin-1.2.3" or "v1.2.3", you can adjust the url in POM accordingly).
            Hide
            Permalink
            zbynek Zbynek Konecny added a comment - - edited

            Hm, maybe this is more tricky: in https://github.com/jenkinsci/ignore-committer-strategy-plugin/blob/master/pom.xml defines URL using a property but it's not geting expanded:, the API sees it as 

            https://github.com/jenkinsci/jenkins-${project.artifactId}-plugin
            Show
            zbynek Zbynek Konecny added a comment - - edited Hm, maybe this is more tricky: in https://github.com/jenkinsci/ignore-committer-strategy-plugin/blob/master/pom.xml defines URL using a property but it's not geting expanded:, the API sees it as https: //github.com/jenkinsci/jenkins-${project.artifactId}-plugin
            Hide
            Permalink
            zbynek Zbynek Konecny added a comment -

            It was implemented in WEBSITE-648, documentation merged in https://github.com/jenkins-infra/jenkins.io/pull/2716

            Show
            zbynek Zbynek Konecny added a comment - It was implemented in  WEBSITE-648 , documentation merged in  https://github.com/jenkins-infra/jenkins.io/pull/2716

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              oleg_nenashev Oleg Nenashev
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: