Remove template npm package test

What does this MR do and why?

Possibly helping to mitigate: #362734 (closed) by decoupling a possible root cause

I think it could be a connectivity issue, especially since it is only on one environment, but I'm curious why the successfully created project might be returning 404's fetching.

It doesn't seem to be happening for other tests that create projects, so maybe it has to do with creating a project with templates?

As I commented in Slack: I think we could remove that template from those npm scenarios. That second project doesn't need to be created from a template. An empty one should work too.

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.

changed milestone to %15.1

added Quality devopspackage grouppackage registry typemaintenance labels

assigned to @svistas

added 1 commit

• d5a50c88 - Remove express template from npm tests

Compare with previous version

Suggested Reviewers (beta)

The individuals below may be good candidates to participate in the review based on various factors.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Suggested Reviewers
@a_mcdonald, @mlapierre, @sliaquat, @chloeliu, @ddavison

If you do not believe these suggestions are useful, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot - an experimental ML-based recommendation engine created by ~"group::applied ml".

	1 Message
	CHANGELOG missing: If you want to create a changelog entry for GitLab FOSS, add the Changelog trailer to the commit message you want to add to the changelog. If you want to create a changelog entry for GitLab EE, also add the EE: true trailer to your commit message. If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

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

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
QA	Will Meek (@willmeek) (UTC+1, 2 hours behind @svistas)	Tiffany Rea (@treagitlab) (UTC-7, 10 hours behind @svistas)

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.

Generated by Danger

Allure report

allure-report-publisher generated test report!

review-qa-blocking: test report for d5a50c88

expand test summary

+-------------------------------------------------------------------+
|                          suites summary                           |
+----------------------+--------+--------+---------+-------+--------+
|                      | passed | failed | skipped | flaky | result |
+----------------------+--------+--------+---------+-------+--------+
| Create               | 23     | 0      | 2       | 23    | ❗     |
| Verify               | 12     | 0      | 1       | 12    | ❗     |
| Package              | 0      | 0      | 1       | 0     | ➖     |
| Plan                 | 41     | 0      | 1       | 41    | ❗     |
| Manage               | 36     | 0      | 2       | 38    | ❗     |
| Version sanity check | 0      | 0      | 1       | 0     | ➖     |
| Protect              | 2      | 0      | 0       | 2     | ❗     |
| Configure            | 0      | 0      | 1       | 0     | ➖     |
+----------------------+--------+--------+---------+-------+--------+
| Total                | 114    | 0      | 9       | 116   | ❗     |
+----------------------+--------+--------+---------+-------+--------+

review-qa-all: test report for d5a50c88

expand test summary

+----------------------------------------------------------+
|                      suites summary                      |
+-------------+--------+--------+---------+-------+--------+
|             | passed | failed | skipped | flaky | result |
+-------------+--------+--------+---------+-------+--------+
| Manage      | 47     | 1      | 7       | 28    | ❌     |
| Create      | 123    | 0      | 5       | 101   | ❗     |
| Verify      | 22     | 0      | 7       | 18    | ❗     |
| Plan        | 11     | 0      | 0       | 9     | ❗     |
| Configure   | 0      | 0      | 2       | 0     | ➖     |
| Non-devops  | 1      | 0      | 1       | 0     | ✅     |
| Secure      | 19     | 0      | 2       | 20    | ❗     |
| Package     | 0      | 0      | 2       | 0     | ➖     |
| Fulfillment | 1      | 0      | 12      | 1     | ❗     |
| Release     | 6      | 0      | 0       | 5     | ❗     |
+-------------+--------+--------+---------+-------+--------+
| Total       | 230    | 1      | 38      | 182   | ❌     |
+-------------+--------+--------+---------+-------+--------+

package-and-qa: test report for d5a50c88

expand test summary

+------------------------------------------------------+
|                    suites summary                    |
+---------+--------+--------+---------+-------+--------+
|         | passed | failed | skipped | flaky | result |
+---------+--------+--------+---------+-------+--------+
| Package | 125    | 0      | 15      | 12    | ❗     |
| Plan    | 3      | 0      | 0       | 0     | ✅     |
+---------+--------+--------+---------+-------+--------+
| Total   | 128    | 0      | 15      | 12    | ❗     |
+---------+--------+--------+---------+-------+--------+

• The gitlab-qa-mirror downstream pipeline for !88261 (d5a50c88) passed.

changed the description

@willmeek can I have a review here? thank you!

requested review from @willmeek

mentioned in issue #362734 (closed)

approved this merge request

requested review from @treagitlab

resolved all threads

approved this merge request

marked the checklist item I have evaluated the MR acceptance checklist for this MR. as completed

merged

@treagitlab, did you forget to run a pipeline before you merged this work? Based on our code review process, if the latest pipeline 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.

(Improve this message?)

mentioned in commit 445abaf5

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 releasedpublished label

added releasedcandidate label and removed releasedpublished label