Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-56571

Credentials Binding page incorrect

    XMLWordPrintable

Details

    Description

      Jenkins Plugins page missing latest release info. Please update.

      Page shows:

      Credentials Binding 1.18

      Last released: 17 days ago

      Changelog

      Version 1.17 (2018-10-29)

      Wiki page also only shows

      Version 1.17 (2018-10-29)

      Attachments

        Activity

          jglick Jesse Glick added a comment -

          Yes I had problems editing the Confluence page at the time, and am apparently still unable to do so. There have been discussions of a projectwide move to using either plain versioned Markdown, or GitHub release notes, as a replacement for such lists in Confluence.

          jglick Jesse Glick added a comment - Yes I had problems editing the Confluence page at the time, and am apparently still unable to do so. There have been discussions of a projectwide move to using either plain versioned Markdown, or GitHub release notes, as a replacement for such lists in Confluence.
          ianw Ian Williams added a comment - - edited

          Ancillary to this this specific issue, it is a general frustration of mine (and presumably others) for the many plugins we depend on seem to present the change information differently. Some display the information on the Jenkins Plugins Index page, some display on a child page on Jenkins Wiki https://wiki.jenkins.io/display/JENKINS/Plugins, (which I understand to be deprecated in favor of https://jenkins.io/, some display on their github CHANGELOG.md or README.md markdown pages, and some simply appear to make a release, leaving it to the user to decipher what changed.This is all very confusing.

          Is there any way to encourage the community to move to a consistent model as the plugins get updated? It would seem the most elegant style is similar to kubernetes, with links to the github CHANGELOG as well as another to the README, detailing the inner workings of the plugin. That, along with a brief overview / background / purpose of the plugin, as well as the rest of the administrivia, eliminates duplication and still conveys the necessary information.

          Any thoughts on a consistent documentation model and how to get to one?

           

          ianw Ian Williams added a comment - - edited Ancillary to this this specific issue, it is a general frustration of mine (and presumably others) for the many plugins we depend on seem to present the change information differently. Some display the information on the Jenkins Plugins Index page, some display on a child page on Jenkins Wiki  https://wiki.jenkins.io/display/JENKINS/Plugins , (which I understand to be deprecated in favor of https://jenkins.io/ , some display on their github CHANGELOG.md or README.md markdown pages, and some simply appear to make a release, leaving it to the user to decipher what changed.This is all very confusing. Is there any way to encourage the community to move to a consistent model as the plugins get updated? It would seem the most elegant style is similar to kubernetes , with links to the github CHANGELOG as well as another to the README, detailing the inner workings of the plugin. That, along with a brief overview / background / purpose of the plugin, as well as the rest of the administrivia, eliminates duplication and still conveys the necessary information. Any thoughts on a consistent documentation model and how to get to one?  
          jglick Jesse Glick added a comment -

          Someone needs to come up with a workable design and file a JEP for it. Out of scope to discuss details here, just thought I would mention the existence of this general frustration.

          jglick Jesse Glick added a comment - Someone needs to come up with a workable design and file a JEP for it. Out of scope to discuss details here, just thought I would mention the existence of this general frustration.

          People

            jglick Jesse Glick
            ianw Ian Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: