Forum Discussion
Hi,
Humm I think I found the root cause.
By Jenkins a TestcompleteService is used and as the system of my target machine is a Win32bit, the service called is a 32bit service.... Not compatible with the Oracle driver installed for TestExecute (64bit).
When I manually launch the test, any service called, only an interaction between TestExecute (64bit) and the Oracle driver (64bit).
I will try to use another slave machine with a Win 64bit and let you know if I'm facing the same issue.
P
- shankar_r7 years agoCommunity Hero
Jenkins, by default it will trigger the 64Bit version of TestComplete/TestExecute.
- porites7 years agoOccasional Contributor
Same issue with a 64bit slave machine.
config:
Slave: Windows 2012 R2 (64bit)
TestComplete: 12.40 (64bit)
Oracle Driver: 12.01 (64bit)
Status of test manually launched --> OK (any provider issue)
Status of same test launched by jenkins job --> KO (provider issue)
Potential root cause: TestComplete Jenkins Plugin
Actually used: v1.8 - 64bit version not managed
Next step: upgrade of the plugin in v1.9
I will let you know :-)
Related Content
- 5 years ago
- 3 years ago
Recent Discussions
- 12 hours ago