|
||||||||
|
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/groups/opt_out.
I can duplicate the problem and believe there is a work around.
If the additional behavior "Force polling using workspace" is added to the Git plugin configuration for the specific job, then I can clone my Visual Studio Online git repository from the Jenkins job.
If I don't add the additional behavior "Force polling using workspace", then the job definition page shows the same error as described in the bug report.
In both those cases, I defined a global credential with my Visual Studio Online user name and password, and used that credential in the Git plugin configuration for the job.
I also can avoid that message if I embed the username and password in the Git URL, though that is much less attractive, since it places the username and password in cleartext in the job definition.