Skip to content

Duplicate global nav tests for upstream projects

Ever since we enabled the test_global_nav_links job for the upstream projects, we see many failures in the docs-site-changes channel. If a failure is from an upstream project, it's safe to ignore it.

However, one has to open the failed pipeline and check if it's from an upstream project. To avoid digging when the failures pop up in Slack, duplicate the test_global_nav_links job and prepend upstream_ in its name, so that we know it's from an upstream project.

Related documentation MR in !3318 (merged)

Edited by Achilleas Pipinellis

Merge request reports