You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/github-on-arm/deploy.md
+11-99Lines changed: 11 additions & 99 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ layout: learningpathall
8
8
9
9
## Overview
10
10
11
-
This section showsyou how to deploy a GitHub Actions self-hosted runner on your Arm64 Google Axion C4A instance. You will install Git and GitHub CLI, authenticate with GitHub, and register the runner so CI/CD workflows run on Arm infrastructure.
11
+
This section shows you how to deploy a GitHub Actions self-hosted runner on your Arm64 Google Axion C4A instance. You will install Git and GitHub CLI, authenticate with GitHub, and register the runner so CI/CD workflows run on Arm infrastructure.
12
12
13
13
## Set up your development environment
14
14
@@ -34,11 +34,11 @@ Authenticate with GitHub:
34
34
gh auth login
35
35
```
36
36
37
-
Follow the prompts and accept the defaults.
37
+
Follow the prompts and accept the defaults:
38
38
39
39
![Login to GitHub alt-text#center](./images/gh-auth.png"Screenshot of GitHub authentication prompt")
40
40
41
-
{{% notice %}}
41
+
{{% notice Note %}}
42
42
If you get an error opening the browser on your virtual machine, you can navigate to the following URL on the host machine and enter the device code displayed in the CLI of the virtual machine:
43
43
```
44
44
https://github.com/login/device
@@ -51,7 +51,7 @@ When authentication succeeds, you will see a confirmation screen in your browser
51
51
52
52
## Test GitHub CLI and Git
53
53
54
-
The command below creates a new public GitHub repository named **test-repo** using the GitHub CLI. It sets the repository visibility to public, meaning that anyone can view it:
54
+
The command below creates a new public GitHub repository named `test-repo` using the GitHub CLI. It sets the repository visibility to public, meaning that anyone can view it:
55
55
56
56
```console
57
57
gh repo create test-repo --public
@@ -71,15 +71,14 @@ You should see an output similar to:
71
71
If the **Actions** tab is not visible, enable Actions under **Settings** → **Actions** → **General** by selecting **Allow all actions and reusable workflows**.
72
72
{{% /notice %}}
73
73
74
-
74
+
![runner alt-text#center](./images/newsh-runner.png"Screenshot of repository Runners settings page")
75
75
76
-
Then, click on the **New self-hosted runner** button. In the **Add new self-hosted runner** section. Select Linux for the operating system, and choose ARM64 for the architecture. This will generate commands to set up the runner. Copy and run them on your Google Axion C4A virtual machine.
76
+
Click **New self-hosted runner**. In the setup panel, choose `Linux` as the operating system and `ARM64` as the architecture. Copy the generated setup commands and run them on your C4A VM.
77
+
78
+
![new-runner alt-text#center](./images/new-runner.png"Screenshot of the Add new self-hosted runner panel")
77
79
78
-
79
-
80
-
The final command links the runner to your GitHub repo using a one-time registration token.
81
-
82
-
During the command’s execution, you will be prompted to provide the runner group, the name of the runner, and the work folder name. You can accept the defaults by pressing **Enter** at each step. The output will resemble as below:
80
+
The final command links the runner to your GitHub repository using a one-time registration token.
81
+
During setup, you will be prompted for the runner group, runner name, and work folder. Press **Enter** at each prompt to accept the defaults. The output should look similar to:
@@ -119,94 +118,7 @@ You should see an output similar to:
119
118
```
120
119
The runner will now be visible in the GitHub actions:
121
120
122
-
121
+
![final-runner alt-text#center](./images/final-runner.png"Screenshot of runner visible in GitHub")
123
122
124
123
For now, you can terminate the `./run.sh` command with `Ctrl+C`. Move on to the next section to set up a simple web server using the runner.
125
-
](./images/gh-auth.png)
126
-
127
-
{{% notice %}}
128
-
If you get an error opening the browser on your virtual machine, you can navigate to the following URL on the host machine.
129
-
```
130
-
https://github.com/login/device
131
-
```
132
-
From there, you can enter the code displayed in the CLI of the virtual machine.
133
-
{{% /notice %}}
134
-
135
-
If the log in was successful, you will see the following confirmation in your browser window.
136
-
137
-
138
-
139
-
### Test GitHub CLI and Git
140
-
141
-
The command below creates a new public GitHub repository named **test-repo** using the GitHub CLI. It sets the repository visibility to public, meaning anyone can view it
142
-
143
-
```console
144
-
gh repo create test-repo --public
145
-
```
146
-
You should see an output similar to:
147
-
```output
148
-
✓ Created repository <your-github-account>/test-repo on GitHub
* Go to your repository's **Settings > Actions**, and under the **Runners** section
156
-
* Click on **Add Runner** or view existing self-hosted runners.
157
-
158
-
{{% notice Note %}}
159
-
If the **Actions** tab is not visible, ensure Actions are enabled by navigating to **Settings > Actions > General**, and select **Allow all actions and reusable workflows**.
160
-
{{% /notice %}}
161
-
162
-
163
124
164
-
Then, click on the **New self-hosted runner** button. In the **Add new self-hosted runner** section. Select Linux for the operating system, and choose ARM64 for the architecture. This will generate commands to set up the runner. Copy and run them on your Google Axion C4A virtual machine.
165
-
166
-
167
-
168
-
The final command links the runner to your GitHub repo using a one-time registration token.
169
-
170
-
During the command’s execution, you will be prompted to provide the runner group, the name of the runner, and the work folder name. You can accept the defaults by pressing **Enter** at each step. The output will resemble as below:
0 commit comments