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/_index.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ minutes_to_complete: 15
6
6
who_is_this_for: This is an introductory topic for developers who want to deploy a GitHub Actions self-hosted runner on an Arm-based Google Axion C4A instance.
7
7
8
8
learning_objectives:
9
-
- Provision an Arm virtual machine on the Google Cloud Platform using the C4A Google Axion instance family.
10
-
- Set up and validate a GitHub Actions self-hosted runner on the Arm virtual machine.
11
-
- Deploy a basic CI workflow with NGINX and verify execution on Arm infrastructure.
9
+
- Provision an Arm virtual machine on the Google Cloud Platform using the C4A Google Axion instance family
10
+
- Set up and validate a GitHub Actions self-hosted runner on the Arm virtual machine
11
+
- Deploy a basic CI workflow with NGINX and verify execution on Arm infrastructure
12
12
13
13
prerequisites:
14
14
- A [Google Cloud Platform (GCP)](https://cloud.google.com/free?utm_source=google&hl=en) account with billing enabled
15
-
- A GitHub account (you can sign up [here](https://github.com/signup))
15
+
- A GitHub account; you can sign up [here](https://github.com/signup)
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/github-on-arm/background.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,12 +16,12 @@ Learn more in Google’s announcement: [Introducing Google Axion processors, our
16
16
17
17
## GitHub Actions and CI/CD
18
18
19
-
GitHub Actions is a powerful CI/CD (Continuous Integration and Continuous Delivery) platform built into GitHub. It allows developers to automate tasks such as building, testing, and deploying code in response to events like code pushes, pull requests, or scheduled jobs—directly from their GitHub repositories. This helps improve development speed, reliability, and collaboration.
19
+
GitHub Actions is a powerful CI/CD (Continuous Integration and Continuous Delivery) platform built into GitHub. It allows developers to automate tasks such as building, testing, and deploying code in response to events like code pushes, pull requests, or scheduled jobs - directly from their GitHub repositories. This helps improve development speed, reliability, and collaboration.
20
20
21
21
A key feature of GitHub Actions is [self-hosted runners](https://docs.github.com/en/actions/concepts/runners/about-self-hosted-runners), which let you run workflows on your own infrastructure instead of GitHub’s hosted servers. This is especially useful for:
22
22
23
-
- Running on custom hardware, including Arm64-based systems (e.g., Google Axion virtual machine), to optimize performance and ensure architecture-specific compatibility.
24
-
- Private network access, allowing secure interaction with internal services or databases.
25
-
- Faster execution, especially for resource-intensive workflows, by using dedicated or high-performance machines.
23
+
- Running on custom hardware, including Arm64-based systems (for example, Google Axion virtual machine), to optimize performance and ensure architecture-specific compatibility
24
+
- Private network access, allowing secure interaction with internal services or databases
25
+
- Faster execution, especially for resource-intensive workflows, by using dedicated or high-performance machines
26
26
27
27
Self-hosted runners give you more control, flexibility, and cost efficiency - ideal for advanced CI/CD pipelines and platform-specific testing.
This section shows how to deploy a self-hosted GitHub Actions runner on your instance. It covers installing Git and GitHub CLI, authenticating with GitHub and configuring the runner on an Arm64 environment for optimized CI/CD workflows.
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
12
12
-
###Set up development environment
13
+
## Set up your development environment
13
14
14
15
Start by installing the required dependencies using the `apt` package manager:
15
16
@@ -18,7 +19,7 @@ sudo apt update
18
19
sudo apt install -y git gh vim
19
20
```
20
21
21
-
Next step is to configure your git credentials. Update the command with your name and email.
Now you are ready to connect the machine to GitHub. The command below is used to authenticate the GitHub CLI with your GitHub account. It allows you to securely log in using a web browser or token, enabling the CLI to interact with repositories, actions, and other GitHub features on your behalf.
29
30
31
+
Authenticate with GitHub:
30
32
31
33
```console
32
34
gh auth login
33
35
```
34
36
35
-
The command will prompt you to make a few choices. For this use-case, you can use the default ones as shown in the image below.
37
+
Follow the prompts and accept the defaults.
36
38
37
-
39
+
![Login to GitHub alt-text#center](./images/gh-auth.png"Screenshot of GitHub authentication prompt")
40
+
41
+
{{% notice %}}
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
+
```
44
+
https://github.com/login/device
45
+
```
46
+
{{% /notice %}}
47
+
48
+
When authentication succeeds, you will see a confirmation screen in your browser:
49
+
50
+
![GitHub UIalt-text#center](./images/login-page.png"Screenshot of successful GitHub login confirmation")
51
+
52
+
## Test GitHub CLI and Git
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:
55
+
56
+
```console
57
+
gh repo create test-repo --public
58
+
```
59
+
You should see an output similar to:
60
+
```output
61
+
✓ Created repository <your-github-account>/test-repo on GitHub
In your repository, go to **Settings** → **Actions** → **Runners** and select **Add runner**, or view existing self-hosted runners.
69
+
70
+
{{% notice Note %}}
71
+
If the **Actions** tab is not visible, enable Actions under **Settings** → **Actions** → **General** by selecting **Allow all actions and reusable workflows**.
72
+
{{% /notice %}}
73
+
74
+
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.
77
+
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:
* Go to your repository's **Settings > Actions**, and under the **Runners** section
68
-
* Click on **Add Runner** or view existing self-hosted runners.
155
+
* Go to your repository's **Settings > Actions**, and under the **Runners** section
156
+
* Click on **Add Runner** or view existing self-hosted runners.
69
157
70
-
{{% notice Note %}}
71
-
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**.
72
-
{{% /notice %}}
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 %}}
73
161
74
-
162
+
75
163
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.
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.
77
165
78
-
166
+
79
167
80
-
The final command links the runner to your GitHub repo using a one-time registration token.
168
+
The final command links the runner to your GitHub repo using a one-time registration token.
81
169
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:
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:
Copy file name to clipboardExpand all lines: content/learning-paths/servers-and-cloud-computing/github-on-arm/instance.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,13 @@ weight: 3
6
6
layout: learningpathall
7
7
---
8
8
9
-
## Introduction
9
+
## Overview
10
10
11
-
This section walks you through creating a **Google Axion C4A Arm virtual machine** on Google Cloud with the **c4a-standard-4 (4 vCPUs, 16 GB memory)** machine type using the **Google Cloud Console**. You will use this VM later as the host for a GitHub Actions self-hosted runner.
11
+
This section walks you through creating a Google Axion C4A Arm virtual machine on Google Cloud with the `c4a-standard-4` (4 vCPUs, 16 GB memory) machine type using the Google Cloud Console. You will use this VM later as the host for a GitHub Actions self-hosted runner.
12
12
13
13
If you don't have a Google Cloud account, see the Learning Path [Getting started with Google Cloud Platform](https://learn.arm.com/learning-paths/servers-and-cloud-computing/csp/google/).
14
14
15
-
###Create an Arm-based virtual machine (C4A)
15
+
## Create an Arm-based virtual machine (C4A)
16
16
17
17
Follow these steps in the Google Cloud Console:
18
18
@@ -26,7 +26,7 @@ Follow these steps in the Google Cloud Console:
26
26
- Under **Networking**, enable **Allow HTTP traffic** so you can test workloads like NGINX later.
27
27
- Select **Create** to launch the instance.
28
28
29
-
![Google Cloud Console page showing C4A VM creation with c4a-standard-4 selected](./images/select-instance.png"Create a C4A VM in the Google Cloud Console")
29
+
![Google Cloud Console page showing C4A VM creation with c4a-standard-4 selectedalt-text#center](./images/select-instance.png"Create a C4A VM in the Google Cloud Console")
30
30
31
31
{{% notice Important %}}
32
32
Do not leave **Allow HTTP traffic** enabled permanently. For long-term use, allow traffic only from the IP addresses you use to connect to the instance.
0 commit comments