LMR QA | Main | Adding a fittin export project
What is currently available
Currently, after !63527 (merged) is merged, the import function is using an export of a sample project which only has one small merge request with one single file changed and zero discussions. It works as a test project to verify that the import setup is working and the tagging of the tests is actually using something else than the API fabrication it would normally use.
What is proposed
There are two options:
1. We use the same project that is used for performance testing (https://staging.gitlab.com/gpt/large_projects/gitlabhq1/-/merge_requests/8785), but since this project is quite large, we will need to prune it of almost everything to reduce the fixture size.
2. We create a custom project that just contains the files that are needed and a merge request that has approximately the same amount of changed files and discussions.
In the end, I chose a mixture of both. I created a project that contains only the files that are later changed by the merge request in the example project. Specifically the commit just before the merge. After that, I used the diff from the merge request and created with it a new branch and merge request. I later added manually all the discussions to match the amount on the example project.
What does this entail
Since the rest of the setup is at this point already up and running, it should be just a replacement of the existing export.tar.gz
file inside the fixture folder.
Relevant links
- The main KR Issue: gitlab-com/www-gitlab-com#11448 (closed)
- Preparing importing MR: !63527 (merged)
- The sample merge request: https://staging.gitlab.com/gpt/large_projects/gitlabhq1/-/merge_requests/8785
- The new sample merge request: tomi/exportable-project!1