we would like to test a Pro team account to integrate vercel in our company Nextjs projects.
Created an account but upon trying to connect GitLab we cannot neither connect the company gitlab account or import a “third party” repo with direct link…
If you’re using self-managed GitLab then that may be the cause of this login error. Vercel is trying to connect to gitlab.com rather than a private instance. You can deploy from self-managed GitLab with Vercel using the CLI and a customized GitLab Pipelines
If you’re using standard GitLab then something else must have caused the problem. Since the error came from the gitlab.com/users/sign_in page, Vercel doesn’t have any specific information about what is going wrong. Please contact GitLab Support. They should be able to help you figure out why your login is not working.
thank you for you hint: maybe that could be the solution, as you correctly guessed our situation.
I’ll keep you posted, as I do believe that is the question and yours… the solution!
Hello there, here from Arkage team tech.
I’m trying to create a CD/CI pipeline. After seeing the How can I use GitLab Pipelines with Vercel? guide I created the gitlab-ci.yml, created the vercel cli project and added to gitlab the required variables BUT,
when I try to merge a pull request to the main branch I recieve an error from GitLab “There has been a timeout failure or the job got stuck. Check your timeout limits or try again”.
Do we have some logs in order to fix these problems?
Thanks,
Emanuele
Thanks for giving it a try, @emanuele18! Since you received the error from GitLab, you would need to access logs from there. I don’t know enough about GitLab logging to offer much guidance on that, but the GitLab Support team should be able to help you find what you need.
I found a couple of Stack Overflow posts that also talk about configuring timeout limits. Sharing them here in case they help you.
You can also use Vercel CLI from your local computer to deploy from source. Running it from your local environment can help you check if there are any problems with the deployment that may have caused the pipeline timeout error.
Hi Amy, thanks for your reply. I have found a log from GitLab. Basically it says which the problem is which I don’t have runners, but in your Guide I didn’t found any mentions about runners. Do you have some suggestions? Or I have to contact GitLab support?
I’ve installed a runner on my local machine for testing purpose and now the pipeline starts but I get this error: Error: You defined "--token", but it's missing a value.
Do you know why?
I’m not sure what would cause the variable to be missing a value. Since the error is happening on GitLab, the their support team will be better able to help you identify the source of the problem.