Gitlab "loses" authentication across multiple projects

Howdy folks,

A while back, we noticed that sometimes our projects wouldn't build automatically. Diving into it, we realised that every so often, they would lose 'authentication' to our Gitlab, meaning that we would need to manually go back in and re-authenticate them.
After looking into this further, it seems like as soon as we authenticate one project, all the other projects lose authentication. The end result of this is that we have to manually re-authenticate a project every 1-2 days, so that it can successfully build itself.

Does anybody have any ideas on how to solve this? It's not a huge problem, but it is incredibly annoying to have to perform some manual steps as part of our otherwise fully automatic pipelines across multiple projects.

 

Same here, we complained about the same problem many time, they claimed "it was fixed", but no, it wasn't. Same problem all the time, across our projects. Before we were able to "fix" this going into Config, EDIT SOURCE CONTROL, but now we have problem also with this. It does not show all our repos, just 4 of them, instead of hundred. When cloud works, it's great, but unfortunately it's only 20% of the time. 80% we have to assist... It it super annoying.

 

It still does this; and if cloudbuild fails for this reason it still adds a cooldown to builds, which is just unfriendly.

 

same problem. if setup gitlab as ci/di token build cancelled without log.
if auth by oauth only one project build work. previous project get auth error...

 

BUT if i setup build with diable windows builder in advanced options (Yes, I'd like to opt out of the new Windows builder infrastructure) build starting with https://tokenName:token@gitlab....git

 

NoMossStudios, new builder infrastructure broken. try build on old.

 

I am having the same problem. Additionally, 90% of the time any edit button in the Config page is greyed out or greyes out after a couple of seconds - so, I have to reload the page about 20 times to change some settings and to solve the mentioned issue I dont even have to change settings. I just have to select my SCM again and then its connected again, Im not even prompted to refresh my Gitlab login.