feat: Downstream Pipeline Jobs

• Please check this box if this contribution uses AI-generated content (including content generated by GitLab Duo features) as outlined in the GitLab DCO & CLA. As a benefit of being a GitLab Community Contributor, you receive complimentary access to GitLab Duo.

Description

For downstream pipelines:

• show downstream jobs
• display job log when downstream job is clicked
• allow cancel, retry, play for downstream job
• support download artifacts for downstream job

Screenshot

To Do Before Merging

• Tim and Tomas to discuss and agree details
• Get all tests passing and pipeline passing
• Follow downstream pipelines recursively (or at least one more level)
• Update contributors file

Related Issues

https://gitlab.com/ubs-group1/ubs/ubs-global/-/issues/361

Resolves #1895 (closed)

How has this been tested?

Manual Integration Tests detailed here

• Downstream pipeline jobs appear
• Click on a downstream job which has finished -> job log appears
• Right-click on a downstream job which has finished, select 'Copy link to clipboard' -> correct link is copied
• Right-click on a downstream job which has finished, select 'Open in GitLab' -> correct link opens in a browser
• Right-click on a downstream job which has finished, select 'Display Log' -> job log appears
• Right-click on a downstream job which has finished, select 'Retry Job' -> job is re-run, new job is visible
• Right-click on a downstream job which has finished, select 'Download Artifacts' -> artifacts are downloaded (only shown for jobs with artifacts)
• Click on a downstream job which is running -> job log appears and gets refreshed as new log lines are written
• Right-click on a downstream job which is running, select 'Cancel Job' -> job is cancelled
• Pipelines with no downstream pipelines are displayed correctly
• Pipelines with one downstream pipeline are displayed correctly
• Pipelines with multiple downstream pipelines are displayed correctly
• Downstream pipelines in the same project are displayed correctly
• Downstream pipelines in a different project are displayed correctly
• Downstream pipelines which have further downstream pipelines are displayed correctly

Screenshots (if appropriate)

What CHANGELOG entry will this MR create?

• fix: Bug fix fixes - a user-facing issue in production - included in changelog
• feature: New feature - a user-facing change which adds functionality - included in changelog
• BREAKING CHANGE: (fix or feature that would cause existing functionality to change) - should bump major version, mentioned in the changelog
• None - other non-user-facing changes