Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Lieutenant Commander
Lieutenant Commander
728 views

Cannot see Jenkins job with parameters in Octane

Jump to solution

We are integrating Octane / Jenkins / UFT.  We have it all set up and working.  We wanted to create a pipeline to the execution job that automatically gets created  in Jenkins.  However, it does not show up in the Job list in the pipeline configuration in Octane.  We think it may have something to do with the parameters set up in the Jenkins job, because if we copy the job and remove the parameters, the copied job shows up in the list.

See attachment for screenshots.

The job in the pipeline config is a manually created job.  This is the job we wanted to create the pipeline for:

"UFT-test-execution-job-Tets-Runner-Id-7001-<ID>"

The Jenkins job parameters are in the screenshots also.  Can anyone tell us why it does not show up in the job list in the pipeline configuration?

0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Hi @scottk13 

if you have created a testrunner using ALM Octane the job on jenkins is created automatically. This job will not show up in the pipeline module as it is parametrized and dedicated to the testrunner implementation of octane. If you want this job "UFT-test-execution-job-Tets-Runner-Id-7001-<ID>" to be listed under the selection of pipeline creation, then follow the instruction by @Radislav Berkovich. However keep in mind, that your testrunner will not work anymore once you add the job as a pipeline in Octane. The job is receiving the suiteId and testsToRun as an input from Octane. If you would remove it it is not going to work anymore. 

Best practice is to seperate TestRunner jobs from the pipeline jobs as they have different focus. The testrunner jobs are focusing on dedicated test execution from a test suite and you can decide what the content of a suite run would be by selecting the tests in octane. While as pipeline jobs are orchestrated outside of Octane. 

Hope this helps.

Cheers,

Amir

View solution in original post

4 Replies
Micro Focus Expert
Micro Focus Expert

Hi.

Generally,  if you want to add this job as pipeline, need to do the following

- rename job so it will not start with "UFT-test", for example to "My_UFT_....."

- remove parameter "suiteId" from job. 

 

Thanks,

Radi.

Micro Focus Expert
Micro Focus Expert

Hi @scottk13 

if you have created a testrunner using ALM Octane the job on jenkins is created automatically. This job will not show up in the pipeline module as it is parametrized and dedicated to the testrunner implementation of octane. If you want this job "UFT-test-execution-job-Tets-Runner-Id-7001-<ID>" to be listed under the selection of pipeline creation, then follow the instruction by @Radislav Berkovich. However keep in mind, that your testrunner will not work anymore once you add the job as a pipeline in Octane. The job is receiving the suiteId and testsToRun as an input from Octane. If you would remove it it is not going to work anymore. 

Best practice is to seperate TestRunner jobs from the pipeline jobs as they have different focus. The testrunner jobs are focusing on dedicated test execution from a test suite and you can decide what the content of a suite run would be by selecting the tests in octane. While as pipeline jobs are orchestrated outside of Octane. 

Hope this helps.

Cheers,

Amir

View solution in original post

Lieutenant Commander
Lieutenant Commander
Thank you for the info. We will definitely keep this in mind.
0 Likes
Lieutenant Commander
Lieutenant Commander
It sounds like we should stick to best practice suggestion and keep our jobs separate. Thank y'all this is great info.
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.