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

Allow setting ID for personal access token

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          Activity

            gpaciga Gregory Paciga created issue -
            mhenschke_atlassian Martin Henschke made changes -
            Field Original Value New Value
            Assignee Kristy Hughes [ khughes ]
            mhenschke_atlassian Martin Henschke made changes -
            Labels tracked-by-atlassian
            gpaciga Gregory Paciga made changes -
            kon Kalle Niemitalo made changes -
            Link This issue is duplicated by JENKINS-66500 [ JENKINS-66500 ]
            kon Kalle Niemitalo made changes -
            Link This issue is duplicated by JENKINS-66500 [ JENKINS-66500 ]
            kon Kalle Niemitalo made changes -
            Link This issue relates to JENKINS-45540 [ JENKINS-45540 ]

            People

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

              Dates

                Created:
                Updated: