Drone doesn't shows any gitlab repo info and fails on every build because of the new token expiry changes on gitlab release

Drone Support
1

On the new Gitlab releases, they have set 2h expiry window on each OAuth2 token (before that release it didn’t have any expiration time).

Currently, when we log in to Drone, after 2hours we will get a 404 error on every repo page on Drone because of the expired GitLab token. It will fail every build as well because can not fetch the repo when running a build.

3 Likes
2

the same thing happens to me is there someone who can tell us why this happens in the drone with the connection to gitlab it didn’t happen before

3

Just as a heads-up, there’s already another topic on this issue with more responses (and a link to a potential fix) - anyone who ends up on this thread should also check the other one.

1 Like