Mark Waite commented on Bug JENKINS-22909

The more I look at this report, the less confident I am that I understand what is requested.

I'm able to clone with a username / password credential without using public / private keys with the following steps:

  1. Configure a global username / password credential (through "Manage Credentials") with appropriate user name and password (no public key, no private key)
  2. Create a new freestyle job - JENKINS-22909-username-password-credentials
  3. Use git as the SCM for the job
  4. Use an ssh URL for the repository. I used ssh://[email protected]/var/lib/git/mwaite/bin.git
  5. Use the previously defined username / password credential as the credential for that ssh URL
  6. Run the job, confirm it succeeds

Are there more steps you're taking to show the problem?

Have you used a more recent git client plugin and a more recent git plugin?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to