You can then navigate in your browser to your GitHub repository, click the Settings tab, and then select Actions and then Runners again in the sidebar, where you should see your newly associated runner with a green dot and a status of Idle, as shown below. Once you’ve completed the setup, you should see the output in the terminal that the runner is up and Listening for Jobs. With that, you can finally execute the run.sh script that will be available in your new runner directory. If your actions require additional environment variables you can add them here as well. And for XCODE_*_DEVELOPER_DIR, provide the path to the Xcode developer directory for the applicable version /Applications/Xcode_12.5.1.app/Contents/Developer.
For ImageOS you need to provide the OS name (macos here) and version in the format macos*version*, i.e. The most important being ImageOS and XCODE_12_DEVELOPER_DIR/ XCODE_11_DEVELOPER_DIR. Then, you can customize the work folder or accept the default value _work.įinally, you need to configure additional environment variables to ensure actions work properly on your self-hosted runner. You can optionally provide additional labels for your runner, the usage of labels will be explained later. Here, choose your runner group and name or accept the default values.
0 kommentar(er)
