My Oracle Support Banner

Test Automation: Jenkins Fails with ERROR :: No valid RUN-ID found. Process will exit. Even When A Test Execution Record is Scheduled. (Doc ID 2971042.1)

Last updated on AUGUST 30, 2023

Applies to:

Siebel CRM - Version 22.10 and later
Information in this document applies to any platform.


When executing a test automation build in Jenkins, sometimes it picks up a test run and sometimes it does not find it.
In both scenarios, the test execution record is scheduled in the application.
There does not seem to be a specific pattern.
It should pick the test execution record at all times

Jenkins output will vary

e.g: this is a successful example:

INFO :: REST GET URL :: /siebel/v1.0/service/Automation Rest Service/GetTestRunId?
INFO :: RUN-ID : 1-2RT8BQA is Picked

and this is a failure example:

INFO :: REST GET URL ::   siebel/v1.0/service/Automation Rest Service/GetTestRunId?
INFO :: RUN-ID : is Picked.
ERROR:: REST GET Call response does not contain valid RUN-ID ::
ERROR :: No valid RUN-ID found. Process will exit.
Finished: SUCCESS

In both cases it ends in "SUCCESS" status but in the second example it did not find a valid row id even though one exists.

The issue can be reproduced at will with the following steps:

1. Log int o Call Center and navigate to Site Map-> Release -> Test Execution
2. Create a test excution record and click schedukle.
3. Log in to Jenkins and execute the build.
4. Notice sometimes it picks up the record and at other times it does not.




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.