ci: Add info message about reusing frontend fixtures

What does this MR do and why?

This is a follow-up of !118601 (merged).

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

assigned to @rymai

added frontend label

Pipeline Changes

This merge request contains changes to the pipeline configuration for the GitLab project.

Please consider the effect of the changes in this merge request on the following:

• Effects on different pipeline types
• Effects on non-canonical projects:
  • gitlab-foss
  • security
  • dev
  • personal forks
• Effects on pipeline performance

Please consider communicating these changes to the broader team following the communication guideline for pipeline changes

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
frontend	Minahil Nichols (@minahilnichols) (UTC-4, 6 hours behind @rymai)	Alexander Turinske (@aturinske) (UTC+12, 10 hours ahead of @rymai)
maintenanceworkflow / maintenancepipelines for CI, Danger	Dzmitry Meshcharakou (@dmeshcharakou) (UTC+2, same timezone as @rymai)	David Dieulivol (@ddieulivol) (UTC+2, same timezone as @rymai)
Engineering Productivity	Reviewer review is optional for Engineering Productivity	Jennifer Li (@jennli) (UTC-7, 9 hours behind @rymai)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

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

Generated by Danger

Proper labels assigned to this merge request. Please ignore me.

@rymai - please see the following guidance and update this merge request.

	1 Error
	Please add typebug typefeature, or typemaintenance label to this merge request.

mentioned in merge request !118601 (merged)

changed the description

changed milestone to %16.0

added Engineering Productivity maintenancepipelines pipeline:mr-approved pipeline:run-as-if-foss typemaintenance workflowcanary labels

removed workflowcanary label

resolved all threads

removed pipeline:mr-approved label

Allure report

allure-report-publisher generated test report!

e2e-review-qa: test report for bbb2c5e8

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Monitor          | 4      | 0      | 0       | 0     | 4     | ✅     |
| Verify           | 10     | 0      | 0       | 0     | 10    | ✅     |
| Plan             | 49     | 0      | 1       | 0     | 50    | ✅     |
| Create           | 28     | 0      | 1       | 0     | 29    | ✅     |
| Data Stores      | 22     | 0      | 0       | 0     | 22    | ✅     |
| Govern           | 24     | 0      | 0       | 0     | 24    | ✅     |
| Manage           | 8      | 0      | 3       | 0     | 11    | ✅     |
| Package          | 0      | 0      | 1       | 0     | 1     | ➖     |
| Framework sanity | 9      | 0      | 1       | 0     | 10    | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 154    | 0      | 7       | 0     | 161   | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+

e2e-package-and-test: test report for bbb2c5e8

expand test summary

+-----------------------------------------------------------------------+
|                            suites summary                             |
+------------------+--------+--------+---------+-------+-------+--------+
|                  | passed | failed | skipped | flaky | total | result |
+------------------+--------+--------+---------+-------+-------+--------+
| Create           | 737    | 0      | 106     | 125   | 843   | ❗     |
| Release          | 30     | 0      | 0       | 20    | 30    | ❗     |
| Verify           | 270    | 0      | 20      | 220   | 290   | ❗     |
| Govern           | 231    | 0      | 0       | 230   | 231   | ❗     |
| Manage           | 214    | 5      | 20      | 48    | 239   | ❌     |
| Data Stores      | 181    | 0      | 3       | 40    | 184   | ❗     |
| Fulfillment      | 12     | 0      | 120     | 0     | 132   | ✅     |
| Plan             | 304    | 0      | 0       | 165   | 304   | ❗     |
| Secure           | 35     | 0      | 25      | 35    | 60    | ❗     |
| Package          | 126    | 0      | 59      | 0     | 185   | ✅     |
| Monitor          | 53     | 1      | 1       | 50    | 55    | ❌     |
| Analytics        | 11     | 0      | 0       | 10    | 11    | ❗     |
| Configure        | 1      | 0      | 15      | 0     | 16    | ✅     |
| ModelOps         | 0      | 0      | 5       | 0     | 5     | ➖     |
| Growth           | 0      | 0      | 10      | 0     | 10    | ➖     |
| Framework sanity | 0      | 0      | 5       | 0     | 5     | ➖     |
| Systems          | 19     | 0      | 0       | 0     | 19    | ✅     |
| GitLab Metrics   | 2      | 0      | 1       | 0     | 3     | ✅     |
+------------------+--------+--------+---------+-------+-------+--------+
| Total            | 2226   | 6      | 390     | 943   | 2622  | ❌     |
+------------------+--------+--------+---------+-------+-------+--------+

@jennli Could you please review? Thanks!

requested review from @jennli

resolved all threads

approved this merge request

@jennli, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

• rspec predictive jobs
• jest predictive jobs
• merging a merge request.

added pipeline:mr-approved label

merged

@jennli, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline was created more than 6 hours ago OR finished more than 2 hours ago, you should:

1. Ensure the merge request is not in Draft status.
2. Start a pipeline (especially important for Community contribution merge requests).
3. Set the merge request to merge when pipeline succeeds.

This is a guideline, not a rule. Please consider replying to this comment for transparency.

This message was generated automatically. You're welcome to improve it.