Update NPM QA specs to use unique package names
Situation
From gitlab-com/gl-infra/production#5908 (comment 730931593), we discovered that using a static package name in the NPM QA specs is not a wise idea. This introduces a flakiness.
Solution
For increased reliability, always unique package names in all package QA specs.
Designs
- Show closed items
Relates to
- #34453714.6
Activity
-
Newest first Oldest first
-
Show all activity Show comments only Show history only
- David Fernandez changed milestone to %Backlog
changed milestone to %Backlog
- David Fernandez set weight to 2
set weight to 2
- David Fernandez mentioned in issue gitlab-com/gl-infra/production#5908 (closed)
mentioned in issue gitlab-com/gl-infra/production#5908 (closed)
- Andrejs Cunskis marked this issue as related to #344537 (closed)
marked this issue as related to #344537 (closed)
- Andrejs Cunskis mentioned in issue #344537 (closed)
mentioned in issue #344537 (closed)
- David Fernandez changed the description
Compare with previous version changed the description
- 🤖 GitLab Bot 🤖 added sectionops label
added sectionops label
- 🤖 GitLab Bot 🤖 added [deprecated] Accepting merge requests label
added [deprecated] Accepting merge requests label
- Maintainer
@10io, please can you add a type label to this issue to help with issue discovery in issue reports. - 🤖 GitLab Bot 🤖 added auto updated label
added auto updated label
- David Fernandez mentioned in merge request !74399 (merged)
mentioned in merge request !74399 (merged)
- David Fernandez mentioned in merge request !74400 (closed)
mentioned in merge request !74400 (closed)
- David Fernandez mentioned in issue gitlab-com/gl-infra/production#5933 (closed)
mentioned in issue gitlab-com/gl-infra/production#5933 (closed)
- David Fernandez mentioned in merge request !74685 (merged)
mentioned in merge request !74685 (merged)
- Author Maintainer
I'm going to split this issue in two:
- use unique package names in all QA specs (this issue)
- add a new spec example to verify that we can’t upload the same package twice on two different projects under the same root group
The reasoning is that I focused in (1.) to increase the reliability of all package specs, not only NPM. As such, this effort has been delivered in %14.6.
I'll open a follow up for (2.).
Collapse replies - Author Maintainer
Follow up for (2.): #346264
- David Fernandez mentioned in issue #346264
mentioned in issue #346264
- David Fernandez changed the description
Compare with previous version changed the description
- Author Maintainer
This has been deployed without incidents.
Closing!
- David Fernandez changed milestone to %14.6
changed milestone to %14.6
- David Fernandez added workflowproduction label
added workflowproduction label
- David Fernandez closed
closed