You are unable to build tfs projects using Jenkins Git plugin, due to what you think is a credential management problem.
The symptoms observed are that once that your pipeline tries to checkout the code the credentials are not properly passed so the script returns an error and the build fails. You also see that your Local scope defined credentials do not show in the credentials dropdown selector.
- CloudBees Core on modern cloud platforms - Managed Master
- CloudBees Core on traditional platforms - Client Master
- CloudBees Jenkins Enterprise - Managed Master
- CloudBees Jenkins Platform - Client Master
- CloudBees Jenkins Distribution
- Jenkins LTS
First of all, you can ignore the error on the repository access using the provided credentials if your master does not have MsBuild installed, as the validation happens inside your master.
The cause for your defined credentials not being available for selection is coming from the fact that the Git plugin is not able to get access to credentials defined out of Global scope. Once that you define your credentials at Global level, you will be able to use them to build the project successfully.
The recommended approach for TFS projects is that you use the Team Foundation Server Plugin, and use personal tokens generated from your TFS server whenever possible.
- CloudBees Core on traditional platforms - Client Master 220.127.116.11-rolling
- Jenkins Git Plugin 3.9.1