Bitbucket Cloud Import Status Page Results in HTTP 500
Summary
When starting import from Bitbucket Cloud, GitLab takes me to Bitbucket import status page: https://gitlab.com/import/bitbucket/status
That page results in HTTP 502 (gateway timeout) most of the time. I believe this is because we have about 1100 repositories in Bitbucket.
This is basically blocking our transition from Bitbucket to GitLab.
Steps to reproduce
- Link Bitbucket Cloud account to GitLab (the Bitbucket account should most likely have access to a lot of repositories -- I have access to about 1100 repositories)
- Open https://gitlab.com/import/bitbucket/status
The issue has gone worse now that we have imported some of our repositories, i.e. at first when we had not done any imports the page loaded fine most of the time. Now when I have imported about 20 repositories the result is HTTP 502 most of the time; like 99%. So the amount of imported projects might affect this (note that our Bitbucket repositories have also been imported by non-bitbucket-admin users so there is more imported repositories than what I have imported).
Example Project
I can help you to reproduce this. The repositories are our company repositories, i.e. those are private.
What is the current bug behavior?
https://gitlab.com/import/bitbucket/status does not load properly (the result is HTTP 502)
What is the expected correct behavior?
https://gitlab.com/import/bitbucket/status should load so that import can be started.
Output of checks
This bug happens on GitLab.com
Possible fixes
List importable repositories (with a possibility to search) and use pagination. Or maybe cache the import status.