Skip to content

Commit 9fd160c

Browse files
authored
added selfhosted workflow ex and notes update
1 parent 2e2ab4a commit 9fd160c

File tree

2 files changed

+34
-0
lines changed

2 files changed

+34
-0
lines changed
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# If you don't create a self-hosted runner you will see:
2+
# Waiting for a runner to pick up this job...
3+
name: Self-hosted Runner Workflow
4+
5+
on:
6+
push:
7+
branches:
8+
- main
9+
10+
jobs:
11+
example-job:
12+
runs-on: self-hosted
13+
steps:
14+
- name: Check out repository
15+
uses: actions/checkout@v3
16+
- name: Run a one-line script
17+
run: echo "Hello from a self-hosted runner!"

Learning-notes/Readme.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -291,3 +291,20 @@ runs-on: self-hosted
291291

292292
If you specify an array of strings or variables, your workflow will execute on any runner that matches all of the specified runs-on values.
293293

294+
#### Self-Hosted Runner
295+
Self-hosted runners can be:
296+
297+
- Physical
298+
- Virtual
299+
- In a container
300+
- On-premises
301+
- In a cloud
302+
303+
You can add self-hosted runners at various levels in the management hierarchy:
304+
305+
- Repository-level runners are dedicated to a single repository.
306+
- Organization-level runners can process jobs for multiple repositories in an organization.
307+
- Enterprise-level runners can be assigned to multiple organizations in an enterprise account.
308+
309+
To set up self-hosted, you need to add a runner and install the **GitHub Actions Runner** to connect the external compute to the self-hosted runner.
310+
After installing the GitHub Actions Runner, ensure **port 443** is open in your outbound rules to allow secure communication between the runner and GitHub.

0 commit comments

Comments
 (0)