Forum Discussion

nisgupta's avatar
nisgupta
Valued Contributor
8 years ago

TestExecute Integration With Jenkins

  We are looking for the ways - how Jenkins can run the projects located in TestExecute machines. Here is our case. At this now now Source code management and so no git.  Jenkins is set up on m...
nisgupta's avatar
nisgupta
Valued Contributor
8 years ago

cunderw

Your updates is giving me lot of information about the jenkins configuration. I have very less experience with Jenkins. Till now I am successful with running the testcomeplete tests on my machine from my local jenkins . 

 

As discussed our main objective is to run the TestComplete tests on TestExecute machines . Currently TestExecute machines do not have jenkins installed Now as per your post, I need to install the jenkins in those machines and then we can configure them ?

 

Thanks

NG

 

 

cunderw's avatar
cunderw
Community Hero
8 years ago

Correct, you have to install the jenkins slave agen on the Test Execute machines and configure them. The preparing jenkins link includes all of the needed details for this to work. If you have any specific issues or problems let us know. 

  • nisgupta's avatar
    nisgupta
    Valued Contributor
    8 years ago

    cunderw 

    shankar_r

     

    Thank you for the updates very much. We are trying to connect the testexecute machines with the jenkins server. there are some issues coming relating to connectivity and our administrator are working to reslove the connectivity issues.  Once those connectivity issues get resolved then will update how it is working or may be we will have some other issues in running tescomplete tests. Will updates once the connectivity issue get resolved.

     

    Thanks

    NG

  • nisgupta's avatar
    nisgupta
    Valued Contributor
    8 years ago

    cunderw

     

    So Now I am launching the jenkins server from the testexecute machine . I have attached the screenshot. 

     

    When I press the lauch button I get the following error 

     

    Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main createEngine

    INFO: Setting up agent: slave_pretty

    Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener <init>

    INFO: Jenkins agent is running in headless mode.

    Sep 27, 2018 9:54:20 AM hudson.remoting.Engine startEngine

    INFO: Using Remoting version: 3.23

    Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir

    INFO: Using C:\Users\nisgupta\Documents\TestComplete\remoting as a remoting work directory

    Sep 27, 2018 9:54:20 AM hudson.remoting.jnlp.Main$CuiListener status

    INFO: Locating server among [http://microcar.ttu.edu:8080/]

    Sep 27, 2018 9:54:20 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve

    INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]

    Sep 27, 2018 9:54:25 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver isPortVisible

    WARNING: connect timed out

    Sep 27, 2018 9:54:25 AM hudson.remoting.jnlp.Main$CuiListener error

    SEVERE: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable

    java.io.IOException: http://microcar.ttu.edu:8080/ provided port:60540 is not reachable

                at org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:286)

                at hudson.remoting.Engine.innerRun(Engine.java:523)

                at hudson.remoting.Engine.run(Engine.java:474)

     

     

     

    • shankar_r's avatar
      shankar_r
      Community Hero
      8 years ago

      Have you followed below steps to activate your slave?

      1. New Node --> Enter Node Name.
      2. Select Dumb Slave --> Press OK.
      3. Fill out the following:
        1. Set a number of executors (one or more) as needed.
        2. Set a Remote FS Root, a home directory for the master on the slave machine.
          1. For a Windows slave, use something like: "C:\Jenkins\"
          2. TODO: add details.
        3. Select the appropriate Usage setting:
          1. For an additional worker: Utilize this slave as much as possible 
          2. For specialized jobs: Leave this machine for tied jobs only
        4. Launch Method:
          1. An easy way to control a Windows slave is by using Launch slave agents via Java Web Start  (Recommended for Windows)
          2. TODO: add steps for other methods.
        5. Availability --> Keep this slave online as much as possible
          1. TODO: add details for each option.
        6. Press OK.
      4. Now you need to connect your slave machine to the master using the following steps.
        1. On you slave machine go to the Jenkins server url.
        2. Go to Manage Jenkins > Manage Nodes, Click on the newly created slave machine.
        3. Click on the Launch button to launch agent from browser on slave.
        4. Run the program.
        5. Now you should see the Slave machine connected under Nodes.
      5. If you want the service to run on start-up of the slave machine do the following (Windows only directions):
        1. In the Slave agent program running on your slave machine, click File --> Install as Windows Service.
        2. Start, type Services and Select the Services program.
        3. Find Jenkins Slave in the list, Double click to open.
        4. Select Startup type --> Automatic.
        5. Go to the Log On tab, change the Log on as to a user of your choice (Special user account Jenkins recommended).
        6. Make sure that auto login is set for the slave machine for the user account, then the VM (or physical computer) should connect and be available when needed.
    • cunderw's avatar
      cunderw
      Community Hero
      8 years ago

      The error is showing that your test execute machine cannot connect to the remote jenkins master whichs sounds like a network / filewall issue. You would probably have to work with your infrastructure team to determine why you are being blocked. 

      • nisgupta's avatar
        nisgupta
        Valued Contributor
        8 years ago

        cunderw

         

        Here is the update 

        we launched the agent from the commandline and it get connected .   and it ran successfully.After connection I set up the Jenkins Project to run the TestComplete Project Suite . So it run the Project Suite located on testexecute machine.

         

         

        But Here is one thing I was looking at the command line which is being used for connection to Jenkins master and get the following exception when I press Build Now

         

        Oct 08, 2018 10:06:34 AM hudson.Util getWin32ErrorMessage

        WARNING: Failed to find resource bundle

        java.util.MissingResourceException: Can't find bundle for base name /hudson/win3

        2errors, locale en_US

                at java.util.ResourceBundle.throwMissingResourceException(Unknown Source

        )

                at java.util.ResourceBundle.getBundleImpl(Unknown Source)

                at java.util.ResourceBundle.getBundle(Unknown Source)

                at hudson.Util.getWin32ErrorMessage(Util.java:662)

                at hudson.util.jna.JnaException.<init>(JnaException.java:37)

                at hudson.util.jna.RegistryKey.check(RegistryKey.java:124)

                at hudson.util.jna.RegistryKey.open(RegistryKey.java:223)

                at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca

        nnerCallable.scanForInstallations(TcInstallationsScanner.java:82)

                at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca

        nnerCallable.call(TcInstallationsScanner.java:69)

                at com.smartbear.jenkins.plugins.testcomplete.TcInstallationsScanner$Sca

        nnerCallable.call(TcInstallationsScanner.java:58)

                at hudson.remoting.UserRequest.perform(UserRequest.java:212)

                at hudson.remoting.UserRequest.perform(UserRequest.java:54)

                at hudson.remoting.Request$2.run(Request.java:369)

                at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecut

        orService.java:72)

                at java.util.concurrent.FutureTask.run(Unknown Source)

                at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

                at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

                at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)

                at java.lang.Thread.run(Unknown Source)

         

        Any idea what is causing this ?

         

        Thanks

        NG