Problem with token when runing job
Summary
My organization uses Gitlab.com where we have several ruby on rails projects. We are running on a free plan. The problem appeared today while automated tests (Job) were running. There is a problem with the expired token (we haven't used token before)
/builds/<organization>/<project>/cache/bundler/ruby/3.1.0/gems/gitlab-4.19.0/lib/gitlab/request.rb:71:in `validate':
Server responded with code 401, message: Token is expired. You can either do re-authorization or token refresh..
Request URI: https://gitlab.com/api/v4/projects/<id>/merge_requests/411/discussions (Gitlab::Error::Unauthorized)
- we are on a free plan, so from what I read we cannot have access tokens turned on. (No such option in project settings)
- on the other hand, job throws an error related to an invalid token
Is this an error or is there something we forgot to include?
Steps to reproduce
none
Example Project
none
What is the current bug behavior?
Stops automated tests and block deployment process
What is the expected correct behavior?
Just do not ask for token like it was before
Relevant logs and/or screenshots
Output of checks
Results of GitLab environment info
Expand for output related to GitLab environment info
Results of GitLab application Check
Expand for output related to the GitLab application check
Possible fixes
Edited by Kamil Walczyk