Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-58613

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

    Details

    • Similar Issues:

      Description

      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.

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              radislavb Radi Berkovich
              Reporter:
              alsteve89 Alberto Stevanato
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: