Forum Discussion

daniele's avatar
daniele
New Contributor
4 years ago

Deploy Slave Project

Hi,

i've a distributed project integrated with TFS in order to execute test by Release (TestComplete v.14.71.275.7 x64).
Project is structured with a Master project and 2 Slave projects that has to work in the related host machine, each of them has a NetworkSuite item with property Deploy : Automatic (other properties available in the General panel are empty).
Test starts properly in debug mode by running network suite from ProjectSuite->Master, while from Release it returns the following error:

Cannot load the remote project. The project file XXXXXXXXXX.mds was not found on the remote computer. Please copy it manually there or modify the network suite's properties to deploy the project to the remote computer automatically

It seems the projects slave aren't copied to host machines once the test is triggered...
Any suggestion about?
I've seen there is following method to execute copy from code:
NetworkSuite.Hosts.ItemByName([HOST_NAME]).CopyProjectToSlave();
Is it necessary?

Thanks

  • Thompsonn  jkrolczy Thanks to everyone for suggestions!
    I confirm Jenkins isn't part of this scenario.
    I've resolved without contact the support by following steps:
    1.Clean manually target folder in the host machines before 

    2.Unbind TestComplete-TFS

    3.Delete then re-map again the project in my local machine being carefully to set a path without empty space or symbol dot in the name of involved folders


    Now the projects are copied properly and test starts as expected by Release

     

9 Replies

  • Thompsonn's avatar
    Thompsonn
    Occasional Visitor
    1. Step 1 − Go to the Manage Jenkins section and scroll down to the section of Manage Nodes.
    2. Step 2 − Click on New Node.
    3. Step 3 − Give a name for the node, choose the Dumb slave option and click on Ok.
    4. Step 4 − Enter the details of the node slave machine.

     

     

     

     

    mygreatlakes

    • jkrolczy's avatar
      jkrolczy
      Regular Contributor

      I did not see a mention of Jenkins being used in the original info posted.

       

      Waiting to see what her reply is back.

    • jkrolczy's avatar
      jkrolczy
      Regular Contributor

      How's this working for you?

       

      From your NetworkSuite: Hosts area: Be sure all columns are filled out.

      There is a Source path column that you may need to add to the Hosts window table.

      Be sure filled out also.

       

      Use the Verify button to verify your settings against your filled out slaves.

      If Verification does not pass, you are not going any further until corrected.

       

      It took me a while to fine tune the NetworkSuite settings and Hosts settings to get my Slaves

      to verify as well as for Copy Project to Slave.

       

      Need any other help or suggestion - let me know.

       

       

       

       

    • daniele's avatar
      daniele
      New Contributor

      Hi TanyaYatskovska ,

       

      i've checked again and seems all preparations are done as per article.

      I'll contact Support team as per your suggested.

      Thank you!

      • daniele's avatar
        daniele
        New Contributor

        Thompsonn  jkrolczy Thanks to everyone for suggestions!
        I confirm Jenkins isn't part of this scenario.
        I've resolved without contact the support by following steps:
        1.Clean manually target folder in the host machines before 

        2.Unbind TestComplete-TFS

        3.Delete then re-map again the project in my local machine being carefully to set a path without empty space or symbol dot in the name of involved folders


        Now the projects are copied properly and test starts as expected by Release