Learning GitHub Actions for DevOps CI/CD - Adding a Self-Hosted Runner

The video tutorial explains how to set up a self-hosted runner for GitHub Actions using a Windows virtual machine on Azure. It covers the steps to configure the runner, including downloading necessary files, running PowerShell commands, and registering the runner with GitHub. The tutorial also discusses adding labels to organize runners and running the runner as a service for automatic startup. The process is verified by checking the runner's status in GitHub.

What is one advantage of adding a self-hosted runner at the organization level?

• It restricts the runner to a single repository.

• It allows for individual repository management.

• It requires less configuration.

• It makes the runner available to multiple repositories.

What is the first step in configuring a self-hosted runner?

• Running the runner as a service.

• Downloading and extracting the runner application.

• Creating a directory for the runner.

• Registering the runner with GitHub.

Which command is used to verify the integrity of the downloaded file?

• Downloading the file again.

• Running the config script.

• Comparing the hash of the file.

• Extracting the file.

What information is required to register the runner with GitHub?

• The runner's hardware specifications.

• The runner's operating system.

• The destination URL and an authentication token.

• The runner's IP address.

Why might you choose to run the runner as a service on Windows?

• To reduce the runner's memory usage.

• To ensure the runner starts automatically after a VM restart.

• To improve the runner's processing speed.

• To allow multiple users to access the runner.

What is the purpose of adding labels to a self-hosted runner?

• To enhance the runner's security features.

• To organize runners based on their characteristics.

• To increase the runner's processing power.

• To limit the runner's access to certain repositories.

What indicates that the runner is ready to take jobs?

• The runner's status is 'error'.

• The runner's status is 'busy'.

• The runner's status is 'idle'.

• The runner's status is 'offline'.