I am unclear what exactly you are trying to accomplish.
yahiatene wrote:
Most of tools dispose of “health check” routine that verify that everything is OK before starting the CI pipeline.
Could you give an example of such a tool?
yahiatene wrote:
So before executing the SoapUI tests in Jenkins I want to verify that :
- - TestRunner of ReadyAPI is available
- - Licences are available in sufficient quantity
- - Each component of the testing tool is ready to use
What would you expect to happen in your pipeline if any of the above fails? And perhaps more importantly: What would expect different from just failing your test run?
yahiatene wrote:
So the point is :
- - What are the best-practices you have observed in IC integration ? What is your advice ?
What I have always done is to keep integration tests in a separate project (both in CMS as well as in CI), chain the projects together, and fail that project run if anything goes wrong. When the project fails, a human is going to have go and investigate, regardless of the failure.
SiKing, thank you for involving into this conversation.
Hi yahiatene , perhaps SiKing could provide you with some valuable advice, please give them the info they are inquiring in case you are still looking for help.
Also, how are things regarding the solution you were going to try, any luck?
Hi sonya_m,
The solution was to request the licence manager of ReadyAPI and get the response in a console output.
The request worked well (see below), but we need a little more information about the licenses manager (existing licenses, available licenses, used licenses), I'm investigating about those statistics and how to get them.
+ /usr/bin/java -jar /opt/tools/ready-api-license-manager/ready-api-license-manager-1.2.6.jar -s IP_adress:port[Pipeline] echoLICENSE MANAGER OUTPUT : Please select the tool for which you want to get the floating license: 1. SoapUI Pro 2. LoadUI Pro 3. Secure (if you have an old license) 4. ServiceV Pro 5. VirtServer Licensed Module: SoapUI Pro License Number: [2018-10-31 00:00:00] ***************** License Type: PROFESSIONAL (floating) Issue Date: 31-Oct-2018 Expiration Date: 25-Jun-2020
Best regards,
Mohamed.
Hi SiKing,
Thank you for your reply, I'll try to be more clear.
SiKing wrote:I am unclear what exactly you are trying to accomplish.
yahiatene wrote:Most of tools dispose of “health check” routine that verify that everything is OK before starting the CI pipeline.
Could you give an example of such a tool?
For example I worked with Jira and HPQC, with both of them we can check their availability and status with some HTTP requests.
yahiatene wrote:So before executing the SoapUI tests in Jenkins I want to verify that :
- - TestRunner of ReadyAPI is available
- - Licences are available in sufficient quantity
- - Each component of the testing tool is ready to use
What would you expect to happen in your pipeline if any of the above fails? And perhaps more importantly: What would expect different from just failing your test run?
What I'm trying to do is a model pipeline to launch fake (blank) tests to see the status of readyAPI and it's License Manager.
For example : if the quantity of licences is insufficient to run the job, the pipeline fails and sends an email to our Tools Expert to check which jobs are using all the licenses. Today we have the console output "No valid license found" just when it fails, and if it's possible we want to have :
4 floating licences found
2 used licenses
2 free licences
yahiatene wrote:So the point is :
- - What are the best-practices you have observed in IC integration ? What is your advice ?
What I have always done is to keep integration tests in a separate project (both in CMS as well as in CI), chain the projects together, and fail that project run if anything goes wrong. When the project fails, a human is going to have go and investigate, regardless of the failure.
So the goal is to make model pipeline, to automate it's run and to do it before production pipeline run.
Best regards,
Mohamed.
