Integrate Arm Virtual Hardware into CI/CD workflow 1
Introduction
Prepare GitHub repository for CI/CD development
Self-hosted runner
Next Steps
Integrate Arm Virtual Hardware into CI/CD workflow 1
Who is this for?
This is an introductory topic for embedded software developers new to Arm Virtual Hardware and its features.
What will you learn?
Upon completion of this Learning Path, you will be able to:
- Prepare a GitHub repository
- Integrate AVH into a CI/CD flow with GitHub Actions
Prerequisites
Before starting, you will need the following:
- Some familiarity with CI/CD concepts is assumed
Summary
This summary was drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
You’ll connect Arm Virtual Hardware (AVH) to a GitHub Actions CI/CD workflow for embedded software. First, you’ll prepare a GitHub repository by forking an example project, generate a Personal Access Token with permission to update workflow files, and set up an AVH instance using the Arm Virtual Hardware install guide. Then, you’ll enable GitHub Actions on the fork and add a self-hosted runner on an AWS host, selecting a Linux image and x64 architecture to match the instance. By the end, you’ll configure the repository to use an AVH-backed self-hosted runner so workflows can drive automated testing and validation for bare‑metal targets.
Frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Enable the token to update GitHub Action workflows. Generate it under Settings > Developer settings > Personal access tokens and save it locally.
Run the commands shown after selecting New self-hosted runner on the machine that will host the runner. Use the AWS instance where Arm Virtual Hardware is set up.
Set Runner image to Linux and Architecture to x64. This matches the AWS instance as specified in the steps.
Open the Actions tab in your fork. If workflows are disabled, click I understand my workflows, go ahead and enable them.
Open Settings > Actions > Runners in the repository and confirm the runner appears in the list. If it doesn’t, re-check the setup commands on the instance.