AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Git remote http basic access denied1/12/2024 The ability to pass a runner registration token was deprecated in GitLab 15.6 and is planned for removal in 17.0, along with support for certain configuration arguments. gitlab-ci.yml?Ĭouldn’t find any other options exept the -t Runner token parameter for the register-command, which doesn’t seem right.Īny suggestions or ideas are highly appreciated/needed :/! However I’m not sure if therefore any other token would be required, maybe inside the. It seems this error is due to the runner not having the right permissions to access private repositories(?) On completion, the runner instance appears on the Gitlab site. This opens a prompt in which the Gitlab-server domain, a registration token and a description have to be entered. When setting up the Gitlab runner, after the Docker container got started, the only command I execute is gitlab-runner register. See Ĭleaning up project directory and file based variables 00:01 The provided password or token is incorrect or your account has 2FA enabled and you must use a personal access token instead of a password. Initialized empty Git repository in /builds/leaflot/tro/.git/ Unfortunately, as soon as the repository is set to private, the pipeline throws the following error in the deployment stage, no matter how often repeated: Fetching changes with git depth set to 20. When the repository is set to being publicly visible, everything works as expected: On every commit the Pipeline finishes successfully and the site is automatigically deployed with Gitlab Pages. if: $CI_COMMIT_BRANCH = $CI_DEFAULT_BRANCH gitlab-ci.yml file for CI: image: node:current-alpine The test-site is just a simple index.html together with the. I’m using the Gitlab Omnibus CE Docker image as well as the official Gitlab runner image from Docker-Hub in order to setup a self-hosted solution for Gitlab pages.
0 Comments
Read More
Leave a Reply. |