Hey guys, I’m evaluating Seed for my company and when trying GitLab integration I ran into this issue on a PR build:

Cloning into 'source'... remote: HTTP Basic: Access denied fatal: Authentication failed for '<https://gitlab.com/mycompany/spikes/serverless-lerna-yarn-starter.git/>

Basically I setup a fresh new pipeline, tested deployment and promotion, and then wandered off for a few hours. Came back to test a PR build and got this failure. Are you by any chance relying on long-lived OAuth tokens? IIRC GitLab deprecated them and since 15.0 is coming up to release perhaps they’ve removed them altogether? (ref: https://northflank.com/blog/supporting-expiring-oauth-access-tokens-for-gitlab). Short-lived tokens expire every 2 hours - and I think this is a fixed interval. Disconnecting and Reconnecting the repo fixed the problem temporarily - but it was dead again by the next day. If it’s what I suspect then this integration will need updating to check the token expiry and refresh if needed.

@Frank same here facing the same problem our engineering is stuck and we cant deploy anything

@Frank Same here, 4 apps - all builds fail with the same error message.

I followed the same mentioned by @Edward Asquith and its working now for the time being though i was scared to do so

IMO I’d give quite strong odds that it’s an expiring token - which takes about 2 hours. It could potentially be a bug on the GitLab side, but it’s also possible they’ve turned off support for something deprecated without giving much warning. They do have a bit of a habit of doing that unfortunately. So it could be affecting other consumers, too.

Ok, it's failing again. The 2 hours after reconnecting seem pretty accurate. This is very unfortunate

issue still not resolved, we are periodically disconnecting and connecting. same with vercel also

@Sourav Sarkar do you know what exactly happened on Gitlab's site? I can't find any information regarding this issue

Sorry for the detail, we are looking into the issue rn.

Brilliant, thanks for the update

Just pushed out a fix to refresh the GitLab access token. Can you guys give this a try: • Go to App Settings page • Disconnect repo • Reconnect repo • Trigger a build You should be able to build successfully after 2 hrs (access token expiry time).

I’ll try that now and retest tomorrow morning UK time

Thanks, trying it now and will let you know tomorrow if it's not working 🙂

Thank you a lot @Frank!

Can confirm this issue appears to be fixed. thanks @Frank. Did you get any visibility into what GitLab changed to cause this?

Same for us too, thanks Frank (&team)!