Include remote triggered job status if available from build console

[smlambert]

For arrangements where some jobs are being triggered on remote servers, attempt to capture the status of those jobs and display appropriately (in grid and tree views).

[jiekang]

An example of a remote triggered job is here:
https://github.com/adoptium/ci-jenkins-pipelines/blob/master/pipelines/build/common/openjdk_build_pipeline.groovy#L592
https://github.com/adoptium/aqa-tests/blob/3e5998a3199bbe54a027e7e9d7e1e04f8697211b/buildenv/jenkins/aqaTestPipeline.groovy#L348

And some sample logs of it (some info removed) in action:

19:55:18  openjdk_build_pipeline: Remote trigger Eclipse Temurin AQA_Test_Pipeline job with x86-64_linux jdk21u
[...]
19:55:18  Remote trigger: sanity.jck,special.jck,dev.jck
[...]
cause=Remote triggered by job [...]
[...]
07:41:50  Waiting for remote jck jobs, sleeping for 20 minutes...
08:01:50  Current extended.jck Status: FINISHED Build status: SUCCESS Remote build URL: [...]
08:01:50  ERROR: sanity.jck,special.jck,dev.jck not successful, setting stage result to: UNSTABLE
08:01:50  Setting overall build result to UNSTABLE

[jiekang]

This might be a little tricky for what I think we'd like to see for the Adoptium instance.

TRSS traverses Jenkins quite well and gets "builds" from "jobs", and builds a tree. E.g:

Job: https://ci.adoptium.net/job/build-scripts/job/release-openjdk21-pipeline/
Build: https://ci.adoptium.net/job/build-scripts/job/release-openjdk21-pipeline/52/

Job: https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.openjdk_x86-64_linux/
Build: https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.openjdk_x86-64_linux/330/

I don't think there is a visible Job and Build for e.g. sanity.jck. If there was, it would be automatic for TRSS to discover it, parse it, and display it in the grid view. The grid already has the jck group supported:
https://github.com/adoptium/aqa-test-tools/blob/master/test-result-summary-client/src/Build/Summary/ResultSummary.jsx#L25

Any enhancements would need to preserve the existing behavior, which I assume is being used by OpenJ9 for their JCK suite.

A few options to consider:

• Modify TRSS to parse the Build output of specific Job types, find "Remote Triggered" builds, and either:
  • Add a dummy "Job" and "Build" to the MongoDB database, that would then be displayed by the UI
  • Use this information only in the "frontend" to display in the UI
• Modify Adoptium Jenkins to have jck jobs that individually perform the remote trigger. These jobs would be triggered in the same parent->child hierarchy of the release-openjdkXX-pipeline jobs that eventually trigger test jobs like hs_sanity.openjdk. The changes to TRSS should be very minimal for this. It should just be additional parsing to apply a "Remote Trigger" UI marker

I'd prefer the modification of the Adoptium Jenkins pipelines.

[smlambert]

Modify TRSS to parse the Build output of specific Job types, find "Remote Triggered" builds, and either:
Add a dummy "Job" and "Build" to the MongoDB database, that would then be displayed by the UI
Use this information only in the "frontend" to display in the UI

This was the option I had in mind. We would modify the build job console output in the section that does the remote trigger, to match the same style of parsing that we use for the test jobs (so we can reuse that piece of code), and pull that out of build job info to populate the UI with job status.

But I do not have a strong preference.