DISCUSS: Where should we put the issues that track failures in nightly images?
I currently create issues that track failures in nightly images in https://gitlab.com/gitlab-org/quality/nightly/issues since it's where the issues are detected and I can use the "Create issue" button from the failing jobs.
That being said, it seems developers are not used to search in this project for existing issues, e.g. https://gitlab.com/gitlab-org/gitlab-ee/issues/7791 duplicates https://gitlab.com/gitlab-org/gitlab-ee/issues/7763 which was created 3 days before and for which I even opened a MR (https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7508). That lead to another two MRs to be created: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7531 and https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/7601.
This means that a lot of time and effort was wasted due to a lack of synchronization/communication.
We should decide where do we want to track the ~"broken master" QA issues:
- In https://gitlab.com/gitlab-org/quality/nightly/issues
- Pros: Central place, do not clutter other projects
- Cons: Not obvious for developers which may search in gitlab-ce / gitlab-ee only
- In https://gitlab.com/gitlab-org/gitlab-ce/issues / https://gitlab.com/gitlab-org/gitlab-ee/issues depending on where the fix will be submitted
- Pros: Default place to search for issues
- Cons: Two separate projects to search for
- In https://gitlab.com/gitlab-org/gitlab-qa/issues
- Pros: Central place, do not clutter other projects
- Cons: gitlab-qa should be around the orchestration framework, not about the instance-level tests
/cc @gl-quality