We have just replaced our old home-grown Jenkins integration with the new 'official' SmartBear Jenkins-TestComplete integration. I find it very easy to work with and it has made our Jenkins integrati...
'
Perhaps I should explain how we have worked around this issue in our current set-up.
In Jenkins we have a 'main' job that calls a row of other Jenkins jobs each of which are a wrapper for 1 TestExecute job. (This way we ensure that the jobs are distributed on the available servers). The main job is being run 1) as a SCM job, 2) timed and 3) through the Jenkins UI. And the subjobs may be run in the same ways.
Each of the subjobs use 'Inject environment variables to the build process' to set a EnvVar. (The value is set in the main job as a string parameter and passed down and is the same for all subjobs). Each of the TE tests include a call to a function that sets a variable in the program. This logic is so that it can either 1) be set 'manually' when starting TC/TE (as an extra parameter in the command line that starts TC/TE, specifically we have a bat-file that passes its argument on to its invokation of TC/TE) and 2) be read of an EnvVar set as described above, if the TE is started automatically.
The purpose of this parametrization is to run in different environments, which is being controlled in the URL of the SaaS.
This may sound complex, but it was relatively easy to set up (though I may not have claimed this just after implementing the solution), and has worked now without any problems whatsoever for over 1/2 year.
Søren Harder, QA/Test engineer, Zmags