nerdexam
GitHub

GITHUB-ACTIONS · Question #13

Which of the following scenarios would require the use of self-hosted runners instead of GitHub- hosted runners?

The correct answer is A. running more than the three concurrent workflows supported by GitHub-hosted runners D. using specialized hardware configurations required for workflows. GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free- tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency.

Configure and manage self-hosted runners

Question

Which of the following scenarios would require the use of self-hosted runners instead of GitHub- hosted runners?

Options

  • Arunning more than the three concurrent workflows supported by GitHub-hosted runners
  • Bexceeding 50,000 monthly minutes of build time
  • Cusing Docker containers as part of the workflow
  • Dusing specialized hardware configurations required for workflows
  • Eperforming builds on macOS

How the community answered

(19 responses)
  • A
    74% (14)
  • B
    5% (1)
  • C
    16% (3)
  • E
    5% (1)

Explanation

GitHub-hosted runners have a limit on the number of concurrent workflows (typically 20 for free- tier accounts and 5 for enterprise). If your organization needs to run more workflows simultaneously, you would need to use self-hosted runners to increase the available concurrency. Self-hosted runners allow you to configure specialized hardware or software setups that are necessary for certain workflows. GitHub-hosted runners may not have access to custom hardware configurations like GPUs or other specialized resources, so self-hosted runners are required in such cases.

Topics

#self-hosted runners#specialized hardware#concurrent workflows#GitHub-hosted limitations

Community Discussion

No community discussion yet for this question.

Full GITHUB-ACTIONS Practice