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.
          Hide
          kazuhidet Kazuhide Takahashi added a comment -

          We will soon release a new version of the Jenkins Xcode Integrate Plugin.
          In this version, compatibility with the current version is maintained. However, major changes have been made to the handling of macOS keychains.
          Information to access the keychain is moved from configuration to credentials.

          Show
          kazuhidet Kazuhide Takahashi added a comment - We will soon release a new version of the Jenkins Xcode Integrate Plugin. In this version, compatibility with the current version is maintained. However, major changes have been made to the handling of macOS keychains. Information to access the keychain is moved from configuration to credentials.
          Hide
          mat1e Mathieu Delrocq added a comment -

          I want to know if this functionnality has been released ?

          Show
          mat1e Mathieu Delrocq added a comment - I want to know if this functionnality has been released ?
          Hide
          kazuhidet Kazuhide Takahashi added a comment -

          Mathieu Delrocq
          Yes! This change has already been included in version 2.0.13.

          Show
          kazuhidet Kazuhide Takahashi added a comment - Mathieu Delrocq Yes! This change has already been included in version 2.0.13.
          Hide
          mat1e Mathieu Delrocq added a comment -

          Thanks you, we found it but we was confused because old keychains fields are always displayed in global configuration but not the Keychain credentials.

          Is it possible to display "Keychain Credentials" in global configuration and remove old fields?

          Show
          mat1e Mathieu Delrocq added a comment - Thanks you, we found it but we was confused because old keychains fields are always displayed in global configuration but not the Keychain credentials. Is it possible to display "Keychain Credentials" in global configuration and remove old fields?
          Hide
          kazuhidet Kazuhide Takahashi added a comment -

          Mathieu Delrocq
          Unfortunately, there is no way to automatically migrate information from the old config to the credentials, so you have to do that yourself.
          And once that's done, you have to remove the old information from the config.

          Show
          kazuhidet Kazuhide Takahashi added a comment - Mathieu Delrocq Unfortunately, there is no way to automatically migrate information from the old config to the credentials, so you have to do that yourself. And once that's done, you have to remove the old information from the config.
          Hide
          mat1e Mathieu Delrocq added a comment -

          Kazuhide Takahashi

          What we'd like, is to see a Keychain credentials field in the global configuration with the xcode-plugin settings.

          Actually there is only old fields wich are deprecated... Of course, olds fields don't have to be removed of the configuration if you judge necessary to keep it.

          But at some point the deprecated fields will have to be deleted.

           

          Show
          mat1e Mathieu Delrocq added a comment - Kazuhide Takahashi What we'd like, is to see a Keychain credentials field in the global configuration with the xcode-plugin settings. Actually there is only old fields wich are deprecated... Of course, olds fields don't have to be removed of the configuration if you judge necessary to keep it. But at some point the deprecated fields will have to be deleted.  

            People

            Assignee:
            kazuhidet Kazuhide Takahashi
            Reporter:
            kazuhidet Kazuhide Takahashi
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: