-
Bug
-
Resolution: Not A Defect
-
Critical
-
Jenkins 2.33, git plugin 3.0.1
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
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
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? 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.
Radha Krishna Srimanthula
added a comment - 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. Radha Krishna Srimanthula
added a comment - Not a defect, this feature is not supported yet. 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"
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"
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