Jenkins HPE Automation Tool Plugin timeout issues - jenkins

I use HPE Automation Tool plugin in Jenkins to run UFT(CI/CD). In the configuration I have put a timeout of 36000 sec(10 hours). Ideally UFT should terminate after 10 hours but it is not terminating and keeps on running.
At the same time if I change the timeout configuration to 2 minutes it works like a charm. But the project that I am working on needs that 10 hours timeout configuration.
UFT version 14.03 is installed in a windows server and the scripts run there.
HPE Automation Tool Plugin version used is 5.2.
Can someone please provide me their inputs, what may the issue?

The plugin uses the QuickTest.Application COM Object to start and control the Test Robot(UFT). I had many issues with UFT running more than 2 hours without any restart (I had my own script driving it) - so I wouldn't assume it is an issue of the Plug-in but of UFT. You could try investigate it further but hey let me tell you my tests:
Have some long tests and run them directly from UFT (Do they run for 10 hours without restart? - mine didn't)
Do the same but drive the execution via a script.
If all those 2 is OK, well then you can assume it is the Plug-in, but again my personal experience with the 2 ways mentioned above led me to the conclusion that it is UFT and not the driver scripts.
What I can propose as an alternative:
Have milestones (Save some Item IDs, critical data somewhere (DB, Files) - restart UFT regularly and reload data stored in the milestone

Related

Delphi GUI test application not working on Jenkins build server

I'm busy implementing a Jenkins build server for Delphi 2007 projects, with DUnit for test applications. The previous solution was built in a very old version of Hudson, with extensive test code and a large scale of production applications. The build scripts are therefore established and I've managed to get the builds going.
However, I'm having some problems with the test applications. These normally work fine from a cmd line execution, which calls TestApp.exe UseTestRunner:Text. However, when running GUI tests, the windows do not popup and the test results are inconsistent.
I suspect it has something to do with the Jenkins service account permissions, but I'm not sure how to proceed. The service currently uses the logged in user account, for various permissions and access to the Delphi environment options that's required for builds. Thus the option to use the Local System account with access to the desktop is tricky and I'm not sure if that will fix the problem.
I'm new to the Jenkins environment and would appreciate any help!

What does the Jenkins iLmBjh process do?

Today I noticed that several of our Jenkins jobs (which are independant, different projects and everything) failed.I investigated an finally listed all processes on the machine that Jenkins uses with the top command. It showed me a very greedy process launched by Jenkins, which name is iLmBjh. Not very clear, isn't it?I tried some things and finally killed it. But it appeared again when I launched a new Jenkins job.Do someone know what this process does? It's the first time I see it on the processes list...
Ok, I guess I found the problem and it's kind of surprising. On our Jenkins instance, we had the JiraTestReporter plugin installed. Our Jira licence ended today. And when I checked the Jenkins logs, it was full of Jira error messages.What is disturbing is that we weren't using it at all... in any of our jobs!I uninstalled it and was able to run my job again. The iLmBjh process did not come back.

Application starting issue websphere application server 8.5 after deployment Jenkins

I am using Jenkins websphere deployer plugin to deploy application to IBM WAS 8.5.5.
The ear deployment is successful but the start up is not successful though Jenkins shows success message.
I assume the ear (around 90MB) takes time for expansion in the remote server, and Jenkins success message is before the complete expansion. Is there a way to delay the process of startup after deployment is done.
Can anyone suggest?
You cannot work around this issue since it requires a modification to the websphere deployer plugin. There is a known synchronization issue for large EAR files. I believe there was a pull request that fixes this issue and was merged into the codebase for v1.3 of the plugin. This version is not yet released but can be viewed on github if you wish to compile and try it out for yourself.
You will need to use maven and to manual imports into your .m2 repository to compile and test this code in jenkins.
Reference: https://github.com/jenkinsci/websphere-deployer-plugin

Jenkins taking different time to build the same file

I have started to use jenkins to build my project. I build my project yesterday and it took me 26 sec to build my flex sdk. I build the same file today and it took me 19 min to build the same file. Could anyone explain how this is happening ? I am trying to optimize my build scripts and I am not able to understand if there is something wrong with my build file or with jenkins.
This is the build that took 19 min
This is the build that took 26 sec
This is my second build running after the first one and the part of MXMLC Compiles took around 27 min out of the total 34 min
Is this happening consistently? Was your system perhaps overloaded when the second build occurred? e.g. A backup running or some CPU-intensive process?
If you install the Timestamper plugin for Jenkins, you will be able to see which parts are taking longer.
Is your Jenkins system on a box all by itself? Is this on Windows?
On Windows systems, files can become locked for all sorts of reasons. I've had problems just because I had a Windows Explore window open up to a directory where Jenkins wanted to overlay a file. Jenkins froze up until I closed my Explorer window. Could this be an issue?
Where is the task being delayed? Install the Jenkins timestamper plugin, and that'll show you what tasks are taking so long. From there, you can narrow down your investigation a bit.

How to run/execute Selenium tests via CI (e.g., Jenkins)

I've started using Play! for an application which we are migrating from Wicket in my organization.
As per our policy, we need to keep all tests up and running via Jenkins and I was able to antify the application and configured Jenkins to call Ant target 'auto-test' successfully.
But it seems like the selenium tests are getting left out.
Is there any way to include/call them from Ant?
Would really appreciate any help.
I am not familiar with selenium, but I know it is possible with Jenkins with some configuration, I think you may find these links helpful
Jenkins Selenium Plugin [1]
Closer to what you need to be doing [2]
If you have anymore questions please feel free to ask.
Goodluck!
Just for a reference, 'auto-test' targets runs the selenium tests as well.
It seems I overlooked the selenium test packs as we have number of suites (app, functional, daos etc...), its my bad.

Resources