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

Credentials dropdown empty even after adding a new credential

      Steps to reproduce:

      1. Create a new job
      2. Select Git as SCM
      3. In the credentials section, click on Add, configure a Secret Text credential (I used a github account)
      4. On the Job Configure page, you'll see that the Credentials dropdown is still none. The newly created credential doesn't show up.

      Issue marked as critical since there is no way I can setup Jenkins to work with Git. If there are workarounds, please let me know.

          [JENKINS-40009] Credentials dropdown empty even after adding a new credential

          Radha Krishna Srimanthula created issue -

          Mark Waite added a comment -

          The git plugin supports username / password based authentication (for https based repository URL's) and ssh private key based authentication (for ssh and scp based repository URL's). You seem to be using an ssh or scp based repository URL, so you'll need to use an ssh private key based credential

          Mark Waite added a comment - The git plugin supports username / password based authentication (for https based repository URL's) and ssh private key based authentication (for ssh and scp based repository URL's). You seem to be using an ssh or scp based repository URL, so you'll need to use an ssh private key based credential
          Mark Waite made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]

          I've tried with https:// scheme as well, with the same result.

          New Credentials using Secret Text are allowed to be created, but are not available in the dropdown box to be selected.

          Is Secret Text scheme broken?

          Radha Krishna Srimanthula added a comment - I've tried with https:// scheme as well, with the same result. New Credentials using Secret Text are allowed to be created, but are not available in the dropdown box to be selected. Is Secret Text scheme broken?
          Radha Krishna Srimanthula made changes -
          Resolution Original: Not A Defect [ 7 ]
          Status Original: Resolved [ 5 ] New: Reopened [ 4 ]
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]

          Mark Waite added a comment -

          sradhakrishna, the secret text scheme is not "broken". It is not supported by the git plugin. You must use either https protocol with a username / password credential, or a private key with ssh/scp protocol.

          Mark Waite added a comment - sradhakrishna , the secret text scheme is not "broken". It is not supported by the git plugin. You must use either https protocol with a username / password credential, or a private key with ssh/scp protocol.

          Thanks for the info Mark!

          May be this should be a feature request then.

          Regards,
          Radha.

          Radha Krishna Srimanthula added a comment - Thanks for the info Mark! May be this should be a feature request then. Regards, Radha.

          Not a defect, this feature is not supported yet.

          Radha Krishna Srimanthula added a comment - Not a defect, this feature is not supported yet.
          Radha Krishna Srimanthula made changes -
          Resolution New: Not A Defect [ 7 ]
          Status Original: Reopened [ 4 ] New: Resolved [ 5 ]

            Unassigned Unassigned
            sradhakrishna Radha Krishna Srimanthula
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: