GitLab: Runner (Windows): Unterschied zwischen den Versionen
Admin (Diskussion | Beiträge) K |
Admin (Diskussion | Beiträge) |
||
Zeile 32: | Zeile 32: | ||
executor = "shell" | executor = "shell" | ||
shell = "powershell" | shell = "powershell" | ||
− | environment = ["HTTP_PROXY=< | + | environment = ["HTTP_PROXY=<your_Proxy>","HTTPS_PROXY=<your_Proxy>"] |
url = "https://<your_GitLab>/" | url = "https://<your_GitLab>/" | ||
token = "<your_token_from_registering_the_runner>" | token = "<your_token_from_registering_the_runner>" | ||
Zeile 43: | Zeile 43: | ||
+ | == Troubleshooting == | ||
+ | === Error: Registering runner... failed runner=xxxx status=couldn't execute POST against..=== | ||
+ | '''Error''' | ||
+ | ''ERROR: Registering runner... failed runner=eGycJT8v status=couldn't execute POST against https://<your_GitLab>/api/v4/runners: Post https://<your_Gitlab>.ch/api/v4/runners: dial tcp <IP>:443: connectex: '' | ||
+ | ''A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.'' | ||
+ | ''PANIC: Failed to register this runner. Perhaps you are having network problems'' | ||
+ | '''Cause''' | ||
+ | In some situations you are not able to register your GitLab-Runner through your proxy, but you can use the following workaround. | ||
+ | |||
+ | '''Workaround / Solution''' | ||
+ | *Run the register process on another machine: | ||
+ | .\gitlab-runner.exe register | ||
+ | *Copy the '''token = <your_Token>''' from inside your new generated '''config.toml'''. | ||
+ | *Add the copied '''token = <your_Token>''' to your GitLab-Runner '''config.toml'''. | ||
+ | *Restart your GitLab-Runner service. | ||
[[Kategorie:PowerShell]] | [[Kategorie:PowerShell]] |
Version vom 20. März 2020, 15:53 Uhr
Inhaltsverzeichnis
[Verbergen]Install GitLab-Runner on Windows as a Windows service
- Create a folder somewhere in your system, ex.: C:\GitLab-Runner.
- Download the binary and put it into the folder you created. Rename the binary to gitlab-runner.exe.
- Run an elevated command prompt.
- Install the Runner as a service and start it. You can either run the service using the Built-in System Account (recommended) or using a user account.
- Run service using Built-in System Account:
.\gitlab-runner.exe install .\gitlab-runner.exe start
- Run service using user account:
.\gitlab-runner.exe install --user <ENTER-YOUR-USERNAME> --password <ENTER-YOUR-PASSWORD> .\gitlab-runner.exe start
- (Optional) Update Runners concurrent value in C:\GitLab-Runner\config.toml to allow multiple concurrent jobs as detailed in advanced configuration details. Additionally you can use the advanced configuration details to update your shell executor to use Bash or PowerShell rather than Batch.
Voila! Runner is installed, running, and will start again after each system reboot. Logs are stored in Windows Event Log More informations: https://docs.gitlab.com/runner/install/windows.html
GitLab Runner behind a proxy
- Add your proxy server in the GitLab Runner configuration "config.toml" (for example):
concurrent = 8 check_interval = 0 log_level = "warning" [session_server] session_timeout = 1800 runners name = "<FQDN>" executor = "shell" shell = "powershell" environment = ["HTTP_PROXY=<your_Proxy>","HTTPS_PROXY=<your_Proxy>"] url = "https://<your_GitLab>/" token = "<your_token_from_registering_the_runner>" tls_verify = false
- Add the following Registry-Key to force the GitLab-Runner service to use the proxy:
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\gitlab-runner\" -Name "Environment" -Value "HTTPS_PROXY=server-proxy.xaas.swissic.ch:8080" -PropertyType MultiString
Troubleshooting
Error: Registering runner... failed runner=xxxx status=couldn't execute POST against..
Error ERROR: Registering runner... failed runner=eGycJT8v status=couldn't execute POST against https://<your_GitLab>/api/v4/runners: Post https://<your_Gitlab>.ch/api/v4/runners: dial tcp <IP>:443: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. PANIC: Failed to register this runner. Perhaps you are having network problems
Cause In some situations you are not able to register your GitLab-Runner through your proxy, but you can use the following workaround.
Workaround / Solution
- Run the register process on another machine:
.\gitlab-runner.exe register
- Copy the token = <your_Token> from inside your new generated config.toml.
- Add the copied token = <your_Token> to your GitLab-Runner config.toml.
- Restart your GitLab-Runner service.