Learning GitHub Actions for DevOps CI/CD - Running Jobs on Self-Hosted Runner

The video tutorial explains how to add and manage self-hosted runners in a GitHub repository. It covers the process of labeling runners, running jobs using PowerShell, and executing workflows. The tutorial also discusses monitoring job status, troubleshooting issues, and cleaning up temporary files. Finally, it demonstrates how to remove a self-hosted runner from GitHub.

What is the purpose of adding labels to self-hosted runners in GitHub Actions?

• To increase the runner's storage capacity

• To improve the runner's security

• To enhance the runner's performance

• To organize runners based on their characteristics

Which tool is used to start a self-hosted runner in the tutorial?

• Terminal

• PowerShell

• Bash

• Command Prompt

How does GitHub determine which runner to use for a job?

• By randomly selecting a runner

• By matching the runner's labels with the job's requirements

• By choosing the runner with the least load

• By selecting the runner with the most storage

What is the purpose of the sleep time in the workflow?

• To simulate a long-running process

• To allow time for manual intervention

• To test the runner's patience

• To delay the job completion for debugging

Where can you find logs for troubleshooting job processing issues on a self-hosted runner?

• In the DIA directory

• In the runner's configuration file

• In the system's main directory

• In the GitHub repository

What happens to the temporary files after a runner job is completed?

• They are archived for future reference

• They are encrypted for security

• They are automatically cleaned up

• They are moved to a backup directory

What is required to remove a self-hosted runner from GitHub?

• The runner's configuration file

• A special removal tool

• A command with a token

• An administrator's approval