Not yet @tobias-trozowski . Thought I would ask here first as I’m an OSS Ultimate Customer. May take this to the Issue boards, but wanted to see how the rest of the community might be experiencing a similar behavior.
Yeah, I’ve seen that too. It’s usually because the runner you’re using is trying to upload artifacts and is getting redirected to a different URL, probably something to do with how GitLab handles its cloud storage.
Just created a GitLab account and having the same problem from the start, being unable to complete a very simple upload with very few files for a static website (Publii). I spent 2 days trying to figure this out only to realise this might just be GitLab not working properly? How is this not an urgent issue if it is affecting many users (both paid and free) for so long? Has anyone found a fix or the reason why this is happening?
The redirect is expected. For SaaS runners, GitLab.com uses an internal clone_url to download Git repository data to save bandwidth costs, but the runner needs to use the public URL to access CI artifacts. This redirection points the runner back to the external URL.