Systems like Gitorious, Gitosis or Github make it easy: you will have to simply copy/paste your key.If you need to setup the authentication with a 'simple' server, look for 'authorized_keys' in this document can read this: to see how to generate the keys.
Interaction with the Git runtime is performed by the use of the Git Client Plugin, which is only tested on official git client. At the project level the Git Plugin is configured by selecting the Git option at the Source Code Management section.
The main section is Repositories where several can be configured. A Repository Browser can also be configured, which adds links in "changes" views within Jenkins to an external system for browsing the details of those changes. Resource Controller.execute(Resource Controller.java:93) at hudson.model. Executor.run(Executor.java:118) Installing the plugin itself works like a charm but configuring the system to work properly under Windows can be a bit tricky. By default, the Jenkins Windows installer sets up Jenkins to run as a service on Windows, which runs as the “Local System account”, NOT your user account.
It's highly system dependent and require user to install and configure adequate tools on all build slaves.
It's based on parsing command output, and as such can be broken by any git cli update - legacy code already check git-cli version to detect which option can be used.
Finally, this URL doesn't require authentication even for secured Jenkins, because the server doesn't directly use anything that the client is sending.