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

Move macOS keychain information from "Configure System" to "Credentials".

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      This is a proposal.
      I would like to change the macOS keychain information defined in "Configure System" in the current Xcode Plugin to defined in "Credentials".
      Because "macOS key chain information" is credential information in the first place.
      And if it is credential, it will be easy to use in other places such as shell script.

        Attachments

          Activity

          Hide
          kazuhidet Kazuhide Takahashi added a comment -

          This modification the specification has been changed so that the keychain information is handled by "Credential Plugin", so there is a problem with compatibility with the past version.

          But Jenkins official document "Writing Pipeline-Compatible Plugins" say "Instead you should integrate with the Credentials plugin."
          https://jenkins.io/doc/developer/plugin-development/pipeline-integration/
          I think this mean Information about authentication had better do it handled through "credential plugin" rather than stored by plugin itself.

          As there are concerns about compatibility etc. with this change, there is also an opinion that this change is against, so as another method, we have prepared a fix that encrypts and stores the password for compatibility.
          https://github.com/jenkinsci/xcode-plugin/pull/102

          Anyway, there is a problem that the password is stored in plain text in the configuration file as it is, so I want to fix this as soon as possible.

          Show
          kazuhidet Kazuhide Takahashi added a comment - This modification the specification has been changed so that the keychain information is handled by "Credential Plugin", so there is a problem with compatibility with the past version. But Jenkins official document "Writing Pipeline-Compatible Plugins" say "Instead you should integrate with the Credentials plugin." https://jenkins.io/doc/developer/plugin-development/pipeline-integration/ I think this mean Information about authentication had better do it handled through "credential plugin" rather than stored by plugin itself. As there are concerns about compatibility etc. with this change, there is also an opinion that this change is against, so as another method, we have prepared a fix that encrypts and stores the password for compatibility. https://github.com/jenkinsci/xcode-plugin/pull/102 Anyway, there is a problem that the password is stored in plain text in the configuration file as it is, so I want to fix this as soon as possible.

            People

            • Assignee:
              Unassigned
              Reporter:
              kazuhidet Kazuhide Takahashi
            • Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: