Highlighted
Respected Contributor.
Respected Contributor.
201 views

Load Generators going Non-Operational overnight causes CI/CD runs to fail in Jenkins

Hi,

I am using Jenkins to trigger Test Runs in performance center.

Sometimes the Load Generators goes Non-Operational and this causes test triggerred from Jenkins to fail. This kills whole purpose of automating runs in Jenkins as this needs manual intervention then.

 

What are the workarounds available to overcome this?

I had tried and used 'HTTP Request' in Build Step in Jenkins to make call to Performance Center Admin Rest API to Authenticate and then Reconfigure Load Generator, below 2 APIs were used:

/Admin/rest/authentication-point/authenticate

Admin/rest/v1/hosts/{host-id}/reconfigure

The problem here is - the 'HTTP Request' in Jenkins does not allow to capture the Cookie from Response Headers from Authenticate API and pass it as Header (Cookie) in subsequent Reconfigure API.

 

Thanks,

Girish

 

 

 

 

0 Likes
2 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Load Generators going Non-Operational overnight causes CI/CD runs to fail in Jenkins

Hello Girish, 

Please share your current Performance Center version. 

Need to validate why the LGs  becomes none operational from time to time. I suggest to open a support case to investigate it.

In addition please use thefollowing hint  which may work as a solution for the authentication: https://stackoverflow.com/questions/12399087/curl-to-access-a-page-that-requires-a-login-from-a-different-page

Aliza

0 Likes
Highlighted
Respected Contributor.
Respected Contributor.

Re: Load Generators going Non-Operational overnight causes CI/CD runs to fail in Jenkins

Hi Aliza,

I overcame this challenge now, used below approach.

1) Used 'Execute Windows Batch Command' in Build Action

2) Made a call to API Suite configured on same Load Generator

3) Reconfigured LG

Also, I noticed that the LG goes Non-Operational while initializing the test in Performance Center. This was due to suspended Controller process running (I am using same machine as LG + Controller). Most probably left behind by previous test.

So executed "Killtask /IM Wlrun.exe /F || true" everytime in Jenkins before kicking off the test.

 

Thanks,

Girish

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.