Retry only once for coverage endpoint

What does this MR do and why?

This is to reduce long running pipelines when mapping is enabled for scheduled runs (for omnibus and CNG pipelines). It works without needing a retry in the gdk pipeline.

For example here the instance job took 78 mins: https://gitlab.com/gitlab-org/gitlab/-/jobs/8279750021#L2597

This MR will help us enable coverband mapping for CNG pipeline without causing long running pipeline for omnibus (where mapping still fails) because same rule governs both pipelines in CI config.

References

Please include cross links to any resources that are relevant to this MR. This will give reviewers and future readers helpful context to give an efficient review of the changes introduced.

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

changed milestone to %17.7

added Sub-DepartmentTest Platform typemaintenance labels

assigned to @hmuralidhar

added pipelinetier-1 label

added QA label

	1 Message
	CHANGELOG missing: If this merge request needs a changelog entry, add the Changelog trailer to the commit message you want to add to the changelog. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Reviewer roulette

Category	Reviewer	Maintainer
QA	@niskhakova (UTC+1, 10 hours behind author)	@ddavison (UTC-5, 16 hours behind author)

Please refer to documentation page for guidance on how you can benefit from the Reviewer Roulette, or use the GitLab Review Workload Dashboard to find other available reviewers.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added Quality label

E2E Test Result Summary

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for cf6986f6

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Create      | 129    | 0      | 22      | 0     | 151   | ✅     |
| Release     | 5      | 0      | 0       | 0     | 5     | ✅     |
| Verify      | 43     | 0      | 2       | 0     | 45    | ✅     |
| Plan        | 76     | 0      | 0       | 0     | 76    | ✅     |
| Package     | 24     | 0      | 11      | 0     | 35    | ✅     |
| Monitor     | 8      | 0      | 0       | 0     | 8     | ✅     |
| Data Stores | 33     | 0      | 1       | 0     | 34    | ✅     |
| Govern      | 75     | 0      | 3       | 0     | 78    | ✅     |
| Secure      | 4      | 0      | 0       | 0     | 4     | ✅     |
| Fulfillment | 2      | 0      | 0       | 0     | 2     | ✅     |
| Manage      | 1      | 0      | 1       | 0     | 2     | ✅     |
| Ai-powered  | 0      | 0      | 1       | 0     | 1     | ➖     |
| Analytics   | 2      | 0      | 0       | 0     | 2     | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 402    | 0      | 41      | 0     | 443   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

e2e-test-on-cng: test report for cf6986f6

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Package     | 24     | 0      | 14      | 0     | 38    | ✅     |
| Verify      | 49     | 0      | 16      | 0     | 65    | ✅     |
| Create      | 136    | 0      | 20      | 0     | 156   | ✅     |
| Govern      | 82     | 0      | 9       | 1     | 91    | ✅     |
| Plan        | 82     | 0      | 8       | 0     | 90    | ✅     |
| Fulfillment | 2      | 0      | 7       | 1     | 9     | ✅     |
| Monitor     | 8      | 0      | 12      | 0     | 20    | ✅     |
| Secure      | 2      | 0      | 5       | 0     | 7     | ✅     |
| Manage      | 1      | 0      | 9       | 0     | 10    | ✅     |
| Release     | 5      | 0      | 1       | 0     | 6     | ✅     |
| Data Stores | 33     | 0      | 10      | 0     | 43    | ✅     |
| Ai-powered  | 0      | 0      | 2       | 0     | 2     | ➖     |
| Analytics   | 2      | 0      | 0       | 1     | 2     | ✅     |
| Growth      | 0      | 0      | 2       | 0     | 2     | ➖     |
| Configure   | 0      | 0      | 3       | 0     | 3     | ➖     |
| ModelOps    | 0      | 0      | 1       | 0     | 1     | ➖     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 426    | 0      | 119     | 3     | 545   | ✅     |
+-------------+--------+--------+---------+-------+-------+--------+

changed the description

requested review from @niskhakova

@niskhakova could you please review this change?

changed the description

approved this merge request

added pipeline:mr-approved label

added pipelinetier-2 label and removed pipelinetier-1 label

Before you set this MR to auto-merge

This merge request will progress on pipeline tiers until it reaches the last tier: pipelinetier-3. We will trigger a new pipeline for each transition to a higher tier.

Before you set this MR to auto-merge, please check the following:

• You are the last maintainer of this merge request
• The latest pipeline for this merge request is pipelinetier-3 (You can find which tier it is in the pipeline name)
• This pipeline is recent enough (created in the last 8 hours)

If all the criteria above apply, please set auto-merge for this merge request.

See pipeline tiers and merging a merge request for more details.

requested review from @ddavison

approved this merge request

added pipelinetier-3 pipeline:run-e2e-omnibus-once labels and removed pipelinetier-2 label

resolved all threads

enabled automatic add to merge train when checks pass

started a merge train

merged

mentioned in commit 82416408

added workflowstaging-canary label

added workflowcanary label and removed workflowstaging-canary label

added workflowstaging label and removed workflowcanary label

added workflowproduction label and removed workflowstaging label

added workflowpost-deploy-db-staging label and removed workflowproduction label

added workflowpost-deploy-db-production label and removed workflowpost-deploy-db-staging label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label