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

Allow setting ID for personal access token

XMLWordPrintable

      When creating a personal access token credential, there is no way to set the credential ID, unlike most other credential types.

      The advantage to being able to do this is that the credential ID can be used in pipelines and JobDSL code in a consistent way across multiple servers. I want to be able to assume in a Job DSL specification that a personal access token must exist with a given ID. As it's currently set up, I have to add the credential to Jenkins to get its randomly assigned ID, and then commit that to my various pipeline scripts.

      I know there are workarounds - e.g. putting the credential ID into an environment variable - but this is out of step with other credential types.

        1. Screen Shot 2021-01-04 at 10.28.01 AM.png
          Screen Shot 2021-01-04 at 10.28.01 AM.png
          14 kB

          [JENKINS-63186] Allow setting ID for personal access token

          Gregory Paciga created issue -
          Martin Henschke made changes -
          Assignee Original: Kristy Hughes [ khughes ]
          Martin Henschke made changes -
          Labels New: tracked-by-atlassian
          Gregory Paciga made changes -
          Attachment New: Screen Shot 2021-01-04 at 10.28.01 AM.png [ 53740 ]
          Kalle Niemitalo made changes -
          Link New: This issue is duplicated by JENKINS-66500 [ JENKINS-66500 ]
          Kalle Niemitalo made changes -
          Link Original: This issue is duplicated by JENKINS-66500 [ JENKINS-66500 ]
          Kalle Niemitalo made changes -
          Link New: This issue relates to JENKINS-45540 [ JENKINS-45540 ]

            Unassigned Unassigned
            gpaciga Gregory Paciga
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: