I have a GitLab account where we have many of our repositories stored inside of groups that are inside of groups. For example, we use the following structure on GitLab.
Group A > Group B > Repository
In this example, Group A is our company name, and Group B is a team internally with a handful of projects.
This seems to cause issue? At least, I seem to have a bunch of GitLab issues that seem to maybe be influenced by this, for example:
When I go to add a new app and import with GitLab (my account is setup fine I believe?), Bitrise always fails after the “Loading provider info, hang tight for a sec…” step, with an error of “Failed to load provider info!”. So I’ve had to manually set up all of my projects with a Gitlab clone URL so far.
After any successful build, on the top of the build page, I see this error: “Unable to send build status back to GitLab. Please check our webhook troubleshooting guide.”
When I click the Source button on the top right of the Project page, (with Gitlab logo, next to Watch button), the corresponding URL gives me a 404 back on GitLab. When I look at the URL path in the browser, it seems to be the right URL, but it’s missing the Group A part of the url path (with example above). So for example, whereas the proper project URL should be https://gitlab.com/group_a/group_b/repository, the Source button links to https://gitlab.com/group_b/repository. This is kinda what lead me to think that the groups inside of groups are what are causing the issue.