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

Credentials dropdown empty even after adding a new credential

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          Hide
          markewaite 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

          Show
          markewaite 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
          Hide
          sradhakrishna 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?

          Show
          sradhakrishna 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?
          Hide
          markewaite Mark Waite added a comment -

          Radha Krishna Srimanthula, 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.

          Show
          markewaite Mark Waite added a comment - Radha Krishna Srimanthula , 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.
          Hide
          sradhakrishna Radha Krishna Srimanthula added a comment -

          Thanks for the info Mark!

          May be this should be a feature request then.

          Regards,
          Radha.

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

          Not a defect, this feature is not supported yet.

          Show
          sradhakrishna Radha Krishna Srimanthula added a comment - Not a defect, this feature is not supported yet.
          Hide
          unlikelyzero John Hill added a comment - - edited

          As a user who is running through the process of checking out a github Jenkinsfile for the first-time, it would be great if this plugin could include in-line helper text to describe which types of credentials are usable instead of hiding non-functional ones.

          I could not determine which plugin "was broken" and only came to the realization that 'Secret Text' could not be used after reading the in-line helper text of the 'Github Branch Source' plugin.

           

          Credentials used to scan branches and pull requests, check out sources and mark commit statuses.
          
          Note that only "username with password" credentials are supported. Existing credentials of other kinds will be filtered out. This is because jenkins exercises GitHub API, and this last one does not support other ways of authentication.
          
          If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub.
          
          If your organization contains private repositories, then you need to specify a credential from an user who have access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo"
          Show
          unlikelyzero John Hill added a comment - - edited As a user who is running through the process of checking out a github Jenkinsfile for the first-time, it would be great if this plugin could include in-line helper text to describe which types of credentials are usable instead of hiding non-functional ones. I could not determine which plugin "was broken" and only came to the realization that 'Secret Text' could not be used after reading the in-line helper text of the 'Github Branch Source' plugin.   Credentials used to scan branches and pull requests, check out sources and mark commit statuses. Note that only "username with password" credentials are supported. Existing credentials of other kinds will be filtered out. This is because jenkins exercises GitHub API, and this last one does not support other ways of authentication. If none is given, only the public repositories will be scanned, and commit status will not be set on GitHub. If your organization contains private repositories, then you need to specify a credential from an user who have access to those repositories. This is done by creating a "username with password" credential where the password is GitHub personal access tokens. The necessary scope is "repo"

            People

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

              Dates

              • Created:
                Updated:
                Resolved: