[JIRA] (JENKINS-58613) Octane pipeline trigger fails when root job has a duplicate name in Jenkins

trslagne@gmail.com (JIRA)

unread,

Jul 23, 2019, 6:03:02 AM7/23/19

to jenkinsc...@googlegroups.com

Alberto Stevanato created an issue

Jenkins /

JENKINS-58613

Octane pipeline trigger fails when root job has a duplicate name in Jenkins

Issue Type:	Bug
Assignee:	Daniel Gront
Components:	hp-application-automation-tools-plugin
Created:	2019-07-23 10:02
Environment:	Jenkins ver. 2.150.2 MF Plugin 5.8 Octane CP10 on-Prem
Labels:	plugin jenkins pipeline octane
Priority:	Critical
Reporter:	Alberto Stevanato

Hello,
When configuring a pipeline in Octane to point to a job which has the same on another job (in a different location) Octane fails in triggering the pointed job, while it triggers the second one.

Example

Job 1: my/job/in/Jenkins --> root job for Octane
Job 2: my/other/job/in/Jenkins --> root job for Octane

Creating a Pipeline on Job 1 and triggering on Octane, it starts the second and data are not sent back. Running the first one from Jenkins, means having partial results back.

Adding the pipeline, Octane correctly sees the jobs path, however.

Don’t know if this is an expected behavior or not.