Skip to content

Collect the artifacts from the same namespace

What does this MR do and why?

Collect the artifacts from the same namespace

The original MR !146489 (merged) fixed pipeline on https://gitlab.com/gitlab-org/security/gitlab/-/merge_requests/3888 for https://gitlab.com/gitlab-org/security/gitlab/-/jobs/6290243869

This was tested in https://gitlab.com/gitlab-org/security/gitlab/-/merge_requests/3919

We need to merge this fix in 16-9-stable-ee too to fix the same problem in a backport MR: https://gitlab.com/gitlab-org/security/gitlab/-/merge_requests/3921/pipelines (failing job: https://gitlab.com/gitlab-org/security/gitlab/-/jobs/6334777828)

MR acceptance checklist

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

  • This MR is backporting a bug fix, documentation update, or spec fix, previously merged in the default branch.
  • The MR that fixed the bug on the default branch has been deployed to GitLab.com (not applicable for documentation or spec changes).
  • This MR has a severity label assigned (if applicable).
  • Set the milestone of the merge request to match the target backport branch version.
  • This MR has been approved by a maintainer (only one approval is required).
  • Ensure the e2e:package-and-test-ee job has either succeeded or been approved by a Software Engineer in Test.

Note to the merge request author and maintainer

If you have questions about the patch release process, please:

Edited by Lin Jen-Shin

Merge request reports

Loading