When configuring a VCS Root for a project hosted on Visual Studio Online, enable alternate credentials support in your VSO account. If required, specify the passphrase to access your SSH key in the corresponding field.įor all the available options to connect to GitHub, please see the comment. When this method is used, specify an absolute path to the private key in the Private Key Path field. Custom Private Key - Supported only for server-side checkout, see TW-18449.Default Private key - Uses the mapping specified in /.ssh/config if the file exists or the private key file /.ssh/id_rsa (the files are required to be present on the server and also on the agent if the agent-side checkout is used).Uploaded Key: uses the key(s) uploaded to the project.Select one of the options from the Private Key list and specify a valid username (if there is no username in the clone URL the username specified here overrides the username from the URL). A private key must be in the OpenSSH format. See TW-18711.įor Git hosted from Team Foundation Server 2013, specify NTLM credentials here. #TEAMCITY GITHUB PASSWORD#Specify a valid username (if there is no username in the clone URL the username specified here overrides the username from the URL) and a password to be used to clone the repository.įor the agent-side checkout, it is supported only if git 1.7.3+ client is installed on the agent. Select this option to clone a repository with anonymous read access. ssh:///repos/test.git, scp-like syntax: Method The following protocols are supported for Git repository URL: When branches are specified here, and if your build configuration has a VCS trigger and a change is found in some branch, TeamCity will trigger a build in this branch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |