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.
- Job 1: my/job/in/ --> root job for Octane
- Job 2: my/other/job/in/ --> 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.