![]() ![]() Whether to lock the Runner to current project : Please enter the gitlab-ci tags for this runner (comma separated): Please enter the gitlab-ci description for this runner: Please enter the gitlab-ci token for this runner: Please enter the gitlab-ci coordinator URL (e.g. ![]() Sudo docker exec -it gitlab-runner /bin/bash ![]() Performing the above steps looks like this: Entering the “Specific Runners” data we retrieved earlier.Issuing the gitlab-runner register command.We could put a configuration together ourselves by looking at the advanced configuration documentation, but that may be a little too advanced for newcomers. This is because the Runner is expecting to find its configuration on our host at /srv/gitlab-runner/config.toml and /etc/gitlab-runner/config.toml on our container. builds=0ĮRROR: Failed to load config stat /etc/gitlab-runner/config.toml: no such file or directory builds=0 Starting multi-runner from /etc/gitlab-runner/config.toml. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |