Team Foundation Server Data Source Credential - Revision history

Rdaly at 16:41, 5 June 2024

2024-06-05T16:41:07Z

← Older revision		Revision as of 16:41, 5 June 2024
Line 1:		Line 1:
	= Creating a Team Foundation Server Data Source Credential =		= Creating an Azure DevOps Server Team Foundation Server (TFS) Data Source Credential =
	[Administrator]		[Administrator]

Rwilliams: /* Creating a Team Foundation Server Data Source Credential */

2024-05-28T15:04:16Z

Creating a Team Foundation Server Data Source Credential

← Older revision		Revision as of 15:04, 28 May 2024
Line 45:		Line 45:
	cd to the ${workspacesDir}		cd to the ${workspacesDir}

	Run ~~this~~ command ~~with the~~ filling in the variables with the values from the Clone errors output as well. The "token" is not shown in the error output for security reasons.		Run the below command filling in the variables with the values from the Clone errors output as well. The "token" is not shown in the error output for security reasons.

	<code>${TF} workspace -new -comment:"New CC Workspace" -collection:${url} -location:local ${tfsWorkspace} "-login:${username},${token}"</code>		<code>${TF} workspace -new -comment:"New CC Workspace" -collection:${url} -location:local ${tfsWorkspace} "-login:${username},${token}"</code>

Rwilliams at 17:02, 24 May 2024

2024-05-24T17:02:35Z

← Older revision		Revision as of 17:02, 24 May 2024
Line 15:		Line 15:
	[[File:TFS azure info pg2.png\|800px]]		[[File:TFS azure info pg2.png\|800px]]
	'''Give the new credential a name'''		'''Give the new credential a name'''
	* Assign it to applicable managers
			* '''Assign it to applicable managers'''
	* '''Select Create'''		* '''Select Create'''

	The system should return to the '''Manage Data Source Credentials''' page with "Credential created" note and the new credential should be listed.		The system should return to the '''Manage Data Source Credentials''' page with "Credential created" note and the new credential should be listed.

	'''Additional ~~Required~~ Step:'''		If during a project initial setup there is an error returned indicating the Clone script FAILED, copy the contents shown under Clone errors and follow the instructions under "Additional EULA Acceptance Step":

			'''Additional EULA Acceptance Step:'''

	When TFS connects for the first time there is a EULA that is passed from Microsoft which must be accepted before any files can be pulled from the repository. Failure to perform this step will result in an error code 100 being returned from the TFS when a project attempts to leverage it to access a file repository. ~~When~~ this occurs capture the error log as there are a number of paramaters that are displayed which will be required to accept the EULA manually.		When TFS connects for the first time there is a EULA that is passed from Microsoft which must be accepted before any files can be pulled from the repository. Failure to perform this step will result in an error code 100 being returned from the TFS when a project attempts to leverage it to access a file repository. If this occurs capture the error log as there are a number of paramaters that are displayed which will be required to accept the EULA manually.

	Note that this step requires logging into the container from the command line.		Note that this step requires logging into the container from the command line.
Line 28:		Line 31:
	The following steps must be performed manually to accept the EULA		The following steps must be performed manually to accept the EULA

	'''Log into the VM containing Docker and the application at the command line'''		'''Log into the VM containing Docker and the application at the command line:'''

			ssh into the VM that contains Docker and the Command Center application.

			'''Log into the Docker container:'''

	~~'''Log into the Docker container'''~~
	Here is the command string for logging into Docker		Here is the command string for logging into Docker

	<code>sudo docker exec -it `sudo docker ps \| grep command-center \| awk '{print $1}' ` bash </code>		<code>sudo docker exec -it `sudo docker ps \| grep command-center \| awk '{print $1}' ` bash </code>

			Once inside the container refer to the Clone errors: section in the log output for the variable values

			cd to the ${workspacesDir}

			Run this command with the filling in the variables with the values from the Clone errors output as well. The "token" is not shown in the error output for security reasons.

			<code>${TF} workspace -new -comment:"New CC Workspace" -collection:${url} -location:local ${tfsWorkspace} "-login:${username},${token}"</code>

			When this runs there should be a return back indicating that the End User License Agreement must be accepted and you need to run tf eula to accept it.

			Run this command

			<code>${TF} eula</code>

			The EULA will be displayed. Go to the end of the document and accept the EULA

			At this point you can exit out of the container by typing exit and then exit the VM.

			'''Confirmation and Validation of EULA acceptance:'''

			The TFS connection should now function as expected in the projects so go back into the Project setup and continue with the configuration. Everything should now be functional

Rwilliams at 16:04, 24 May 2024

2024-05-24T16:04:25Z

← Older revision		Revision as of 16:04, 24 May 2024
Line 19:		Line 19:

	The system should return to the '''Manage Data Source Credentials''' page with "Credential created" note and the new credential should be listed.		The system should return to the '''Manage Data Source Credentials''' page with "Credential created" note and the new credential should be listed.

			'''Additional Required Step:'''

			When TFS connects for the first time there is a EULA that is passed from Microsoft which must be accepted before any files can be pulled from the repository. Failure to perform this step will result in an error code 100 being returned from the TFS when a project attempts to leverage it to access a file repository. When this occurs capture the error log as there are a number of paramaters that are displayed which will be required to accept the EULA manually.

			Note that this step requires logging into the container from the command line.

			The following steps must be performed manually to accept the EULA

			'''Log into the VM containing Docker and the application at the command line'''

			'''Log into the Docker container'''
			Here is the command string for logging into Docker

			<code>sudo docker exec -it `sudo docker ps \| grep command-center \| awk '{print $1}' ` bash </code>

Rwilliams: /* Creating a Team Foundation Server Data Source Credential */

2024-05-24T15:11:18Z

Creating a Team Foundation Server Data Source Credential

← Older revision		Revision as of 15:11, 24 May 2024
Line 17:		Line 17:
	* Assign it to applicable managers		* Assign it to applicable managers
	* '''Select Create'''		* '''Select Create'''

			The system should return to the '''Manage Data Source Credentials''' page with "Credential created" note and the new credential should be listed.

Rwilliams: /* Creating a Team Foundation Server Data Source Credential */

2024-05-24T15:10:23Z

Creating a Team Foundation Server Data Source Credential

← Older revision		Revision as of 15:10, 24 May 2024
Line 10:		Line 10:

	[[File:TFS azure info page.png\|800px]]		[[File:TFS azure info page.png\|800px]]
			'''Enter a Username, Token and the TFS Callback URL '''
			* '''Select Next'''

	[[File:TFS azure info pg2.png\|800px]]		[[File:TFS azure info pg2.png\|800px]]
			'''Give the new credential a name'''
			* Assign it to applicable managers
			* '''Select Create'''

Rwilliams: Created page with "= Creating a Team Foundation Server Data Source Credential = [Administrator] The Administrator can create the data source credentials by selecting the File:CreateIcon.jpg|3..."

2024-05-24T15:07:39Z

Created page with "= Creating a Team Foundation Server Data Source Credential = [Administrator] The Administrator can create the data source credentials by selecting the File:CreateIcon.jpg|3..."

New page

= Creating a Team Foundation Server Data Source Credential =
[Administrator]

The Administrator can create the data source credentials by selecting the [[File:CreateIcon.jpg|30px]] ('''Create new credential''') button on the Manage Data Source Credentials page.

'''Select the Azure DevOps Server (TFS) card'''

[[File:Azure devops tfs card.png|100px]]

[[File:TFS azure info page.png|800px]]

[[File:TFS azure info pg2.png|800px]]