Background:

• We use the Yet Another Build Visualizer plugin to display the build flow of many of our Jenkins jobs where there are upstream/downstream job relationships.
• The Yet Another Build Visualizer plugin depends on the Downstream Build Cache Plugin - to determine upstream and downstream builds.

Problem:

When the option Build other remote/local jobs from the Operations Center Context is added to a job, it doesn't display as a downstream job that was triggered by an upstream job.

Sample recreate case:

I have a test job called upstream-job.

The upstream-job has 2 different Post-build actions configured as follows

1. Build other remote/local jobs from the Operations Center Context
   Where the job is configured to trigger downstream-job1

1. Trigger parameterized build on other projects from the Jenkins Parameterized Trigger plugin
   Where the job is configured to trigger downstream-job2 and downstream-job3

If I trigger the upstream-job and view the graph generated by the Yet another build visualizer graph, it only displays downstream-job2 and downstream-job3 but not downstream-job1 even though it was successfully triggered.

Possible reason for the problem?

I am not certain if this is the root cause or not, but on a controller I have, let's call it Controller A, the Downstream Build Cache Plugin installed which appears to be a requirement for the Yet Another Build Visualizer plugin.

However at the operations center context (cjoc cloudbees enterprise parent controller), this plugin is not installed (nor available to be installed by me.)

So, my question is - Is there a way to visualize upstream/downstream builds when using the Build other remote/local jobs from the Operations Center Context either by installing the plugin at the Operations Center level or by some other means.

Business case

The business rationale for this is that we have the following use case:

1. Upstream job performs a deployment
2. After the upstream deployment is complete we trigger several downstream test jobs. Some of these jobs are configured on the same Jenkins controller (Controller A), but some of these jobs are triggered on a different Jenkins controller (Controller B). We'd like to be able to see/visualize all of the downstream automation jobs that are triggered from the upstream job to be able to tell at a glance which tests have passed/failed, but this doesn't currently seem possible using the Build other remote/local jobs from the Operations Center Context