Forum Discussion

malj's avatar
malj
Contributor
5 years ago

Running Report Generator on a Jenkins slave

I am trying to launch SmartBear Report Generator to be able to generate a report when TestExecute hangs on any of our Jenkins slaves, which happens intermittently. I have been told by support to run ...
  • malj's avatar
    malj
    5 years ago

    The support engineer reproduced the problem with launching Report Generator using an "Execute Windows batch command" build step. The problem is that is creates a "headless session". When the TestComplete plugin creates a session for the test, it is another session, i.e. the Report Generator and TestComplete are launched in different sessions. 

    We successfully used a different approach to make the Report Generator and TestComplete run in the same session. We added script to our TestComplete project (see below) to execute Report Generator as the very first step. 

     

    We added the following to our Python scripts: 

     

    cmd = '\"C:\\Program Files (x86)\\SmartBear\\TestExecute 14\\x64\\Bin\\ReportGenerator.exe\" --desktop SE.SBO.WorkStation.exe --generate-report C:\\dev --storage-directory C:\\dev'
shell = Sys.OleObject['WScript.Shell']
shell.Run(cmd, 1, False)

    This works well for us.

AlexKaras's avatar
AlexKaras
Champion Level 3

Hi,

 

Just a wild guess - do you have an active user desktop session on the Jenkins slave when Jenkins tries to start Report Generator?

 

P.S. Why not to continue to work with Support and ask they as well?

 

malj's avatar
malj
Contributor
5 years ago

The result is the same whether I am logged-in to the slave via Remote Desktop Connection or not during the build.

 

I am still working on this with support but it is taking a lot of time. Usually I can get quicker response here. 

  • AlexKaras's avatar
    AlexKaras
    Champion Level 3
    5 years ago

    Hi,

     

    Sorry, but no other good ideas at the moment... :(

    Another reincarnation of my question, just to be on the safe side:

    Is Jenkins slave that starts Report Generator runs as an application but not as a service (which is the default)?

     

    • malj's avatar
      malj
      Contributor
      5 years ago

      Not sure what you mean. We have a Jenkins service and a TestComplete service running but I suppose the TestComplete service is not involved until the TestComplete Test build step starts.

       

      If I replace the suggested command line with "C:\Windows\notepad.exe", Notepad will launch. That makes me think this is some kind of permission issue.

      • AlexKaras's avatar
        AlexKaras
        Champion Level 3
        5 years ago

        malj :

        Hi,

         

        > Not sure what you mean.

        Ah, I probably used wrong names.

        When Jenkins server sends commands to the slave, it (server) communicates with the Jenkins Agent running on this slave. Agent can be started either as a Windows service (which is the default) or as a regular Windows application. The latter option is required in order for TestComplete to be started in the active user session.

        I thought that it may be required to have Report Generator to run in the active user session as well.

        However, considering the fact that Notepad starts fine and starts in the user session, your setup for the Jenkins slave seems to be correct...

         

        P.S. One more idea :

        > command line [...]

        > [...] an "Execute Windows batch command" build step

        I guess that this build step starts command-line processor (cmd.exe) and passes parameter (command line) to it.

        If this is the case, then, for complex command lines that contain not only the name of the executable to launch but also a set of parameters, the whole command line must be included in doubled quotes in order to be passed as a whole to command-line processor.

        Something like this:

        """C:\Program Files (x86)\SmartBear\TestExecute 14\Bin\ReportGenerator.exe" --desktop SE.SBO.WorkStation --generate-report C:\temp\DebugTrace --storage-directory C:\temp\DebugTrace""

        Does this help?