Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies reply
    1
  • Answers answer
    1
  • Subscribers subscribers
    11
  • Views views
    451
  • Users 0 members are here
Related
Options

UFT Developer Runtime engine not getting started on Jenkins Slave machine

Kamal Bora

I am running my test on Jenkins slave machine which is connected via Jenkins agent as service.

UFT developer runtime engine is not getting enabled on the slave machine when I trigger build from Jenkins server but when I run directly in Jenkins slave the runtime engine gets started.

I even tried executing leanft.bat file to get engine started via putting it as part of Execute Batch command in Jenkins but sill its not getting started in slave whereas if I directly run the bat file in slave it works fine.

Is there something wrong I am doing.

  • Suggested Answer

    0  

    when you are running UFT Developer from CICD like Jenkins you should ensure that the Jenkins agent has the right user and privileges.

    By default, the Jenkins agent runs under SYSTEM user and session 0 this session is not an interactive session which our engine needs in order to perform the GUI operations.

    Please try to give to the Jenkins service an interactive user/domain user.

    By doing this you should be able to start the engine from Jenkins.

    Corneliu,

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.