Hi all,
I have the following scenario:
A. My team works in a project using Visual Studio Online
B. The team members have Visual Studio Premium licences activated.
C. The machines that we indented to have for Continuous Delivery process will be placed in Azure.
D. The machines that will host the build controller, build agents, test controller and test agents will also be created in Azure.
What we accomplished so far in Azure:
1. We have created a Virtual network.
2. We have created an active directory where we added all team member accounts. (azure active directory service)
3. We have created a CI machine joined in the Virtual Network.
4. We have created a Build controller machine that has 2 build agents, also joined in Virtual Network.
5. We were able to use this build controller from Visual Studio Online to perform a build operation.
6. We have created a test controller machine and a test agent machine that were successfully configured (based on their wizard)
We used for test agent configuration wizard a user that is admin on that machine in the "Run test agent as a service" section.
In "Register with test controller" section we used #TestControllerIP#:6901.
For the test controller configuration, the first time we tried to install it on a different machine than build controller without success - we were not able to integrate it with Visual Studio Online.
Second approach was to install test controller on same machine as with the build controller and here we successfully configured it using:
in "specify the logon account for the test controller service" section, we used the local admin account.
In "register test controller with team project collection" section we used https://#Project#.visualstudio.com/DefaultCollection
Also we used the same local user in "use a lab service account to communicate with test controller" section.
The wizard configuration tool run successfully.
7. in Visual Studio, we created an empty test settings file that we were unable to configure:
In general section for its configuration wizard, we chose "run test using local computer or test controller"
In Roles section, from "test execution method" drop down we choose Remote execution, from controller we choose Manage test controller, use the name of test controller machine (in our case build controller machine name from azure).
Note: We add in hosts file, this name and the public IP of the build controller machine.
The error is: THE SERVER HAS REJECTED THE CLIENT CREDENTIALS.
I assume that the credentials used to connect to test controller machine are my Visual Studio Online credentials that has nothing to do with test controller/build controller machine.
What we did wrong?
Should we have a domain controller that manage all of these machine in Azure and should we use for the configuration our Azure/Visual Studio accounts instead of local account?
There is any step that we skip in this process?
Please advice. Thank you.
I have the following scenario:
A. My team works in a project using Visual Studio Online
B. The team members have Visual Studio Premium licences activated.
C. The machines that we indented to have for Continuous Delivery process will be placed in Azure.
D. The machines that will host the build controller, build agents, test controller and test agents will also be created in Azure.
What we accomplished so far in Azure:
1. We have created a Virtual network.
2. We have created an active directory where we added all team member accounts. (azure active directory service)
3. We have created a CI machine joined in the Virtual Network.
4. We have created a Build controller machine that has 2 build agents, also joined in Virtual Network.
5. We were able to use this build controller from Visual Studio Online to perform a build operation.
6. We have created a test controller machine and a test agent machine that were successfully configured (based on their wizard)
We used for test agent configuration wizard a user that is admin on that machine in the "Run test agent as a service" section.
In "Register with test controller" section we used #TestControllerIP#:6901.
For the test controller configuration, the first time we tried to install it on a different machine than build controller without success - we were not able to integrate it with Visual Studio Online.
Second approach was to install test controller on same machine as with the build controller and here we successfully configured it using:
in "specify the logon account for the test controller service" section, we used the local admin account.
In "register test controller with team project collection" section we used https://#Project#.visualstudio.com/DefaultCollection
Also we used the same local user in "use a lab service account to communicate with test controller" section.
The wizard configuration tool run successfully.
7. in Visual Studio, we created an empty test settings file that we were unable to configure:
In general section for its configuration wizard, we chose "run test using local computer or test controller"
In Roles section, from "test execution method" drop down we choose Remote execution, from controller we choose Manage test controller, use the name of test controller machine (in our case build controller machine name from azure).
Note: We add in hosts file, this name and the public IP of the build controller machine.
The error is: THE SERVER HAS REJECTED THE CLIENT CREDENTIALS.
I assume that the credentials used to connect to test controller machine are my Visual Studio Online credentials that has nothing to do with test controller/build controller machine.
What we did wrong?
Should we have a domain controller that manage all of these machine in Azure and should we use for the configuration our Azure/Visual Studio accounts instead of local account?
There is any step that we skip in this process?
Please advice. Thank you.