Add GHA workflows for additional device types

Change-type: patch
Signed-off-by: Kyle Harding <[email protected]>

.github/workflows/beaglebone.yml

@@ -0,0 +1,38 @@
+name: BeagleBone Black
+
+on:
+  # With these triggers the Yocto jobs will run
+  # in parallel with the Flowzone jobs, which is fine for now
+  # and allows us to better control what we want to test and when.
+  # It is expected that Flowzone could fail, but yocto jobs will run.
+  pull_request:
+    branches:
+      - "main"
+      - "master"
+  pull_request_target:
+    branches:
+      - "main"
+      - "master"
+
+jobs:
+  yocto:
+    name: Yocto
+    # FIXME: This workflow has dependencies on scripts in the balena-yocto-scripts repository
+    # which is pinned separately as a submodule in the device repo. Expect some drift but try to retain compatibility.
+    uses: balena-os/balena-yocto-scripts/.github/workflows/[email protected]
+    # Prevent duplicate workflow executions for pull_request (PR) and pull_request_target (PRT) events.
+    # Both PR and PRT will be triggered for the same pull request, whether it is internal or from a fork.
+    # This condition will prevent the workflow from running twice for the same pull request while
+    # still allowing it to run for all other event types.
+    if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
+    secrets: inherit
+    with:
+      machine: beaglebone
+      device-repo: balena-os/balena-beaglebone
+      device-repo-ref: master
+      # Pin to the current commit
+      meta-balena-ref: ${{ github.sha }}
+      # Don't deploy any artifacts for meta-balena build sanity workflows
+      deploy-s3: false
+      deploy-hostapp: false
+      deploy-ami: false

.github/workflows/generic-aarch64.yml

@@ -0,0 +1,47 @@
+name: Generic AARCH64
+
+on:
+  # With these triggers the Yocto jobs will run
+  # in parallel with the Flowzone jobs, which is fine for now
+  # and allows us to better control what we want to test and when.
+  # It is expected that Flowzone could fail, but yocto jobs will run.
+  pull_request:
+    branches:
+      - "main"
+      - "master"
+  pull_request_target:
+    branches:
+      - "main"
+      - "master"
+
+jobs:
+  yocto:
+    name: Yocto
+    # FIXME: This workflow has dependencies on scripts in the balena-yocto-scripts repository
+    # which is pinned separately as a submodule in the device repo. Expect some drift but try to retain compatibility.
+    uses: balena-os/balena-yocto-scripts/.github/workflows/[email protected]
+    # Prevent duplicate workflow executions for pull_request (PR) and pull_request_target (PRT) events.
+    # Both PR and PRT will be triggered for the same pull request, whether it is internal or from a fork.
+    # This condition will prevent the workflow from running twice for the same pull request while
+    # still allowing it to run for all other event types.
+    if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
+    secrets: inherit
+    with:
+      machine: generic-aarch64
+      device-repo: balena-os/balena-generic
+      device-repo-ref: master
+      # Pin to the current commit
+      meta-balena-ref: ${{ github.sha }}
+      # Don't deploy any artifacts for meta-balena build sanity workflows
+      deploy-s3: false
+      deploy-hostapp: false
+      deploy-ami: false
+      # Use QEMU workers for testing and run cloud suite against balenaCloud production
+      # This would be faster with KVM on ARM64 but nested KVM is only on x86_64
+      test_matrix: >
+        {
+          "test_suite": ["os","cloud","hup"],
+          "environment": ["balena-cloud.com"],
+          "worker_type": ["qemu"],
+          "runs_on": [["self-hosted", "X64", "kvm"]]
+        }

.github/workflows/jetson-nano.yml

@@ -0,0 +1,38 @@
+name: Nvidia Jetson Nano SD-CARD
+
+on:
+  # With these triggers the Yocto jobs will run
+  # in parallel with the Flowzone jobs, which is fine for now
+  # and allows us to better control what we want to test and when.
+  # It is expected that Flowzone could fail, but yocto jobs will run.
+  pull_request:
+    branches:
+      - "main"
+      - "master"
+  pull_request_target:
+    branches:
+      - "main"
+      - "master"
+
+jobs:
+  yocto:
+    name: Yocto
+    # FIXME: This workflow has dependencies on scripts in the balena-yocto-scripts repository
+    # which is pinned separately as a submodule in the device repo. Expect some drift but try to retain compatibility.
+    uses: balena-os/balena-yocto-scripts/.github/workflows/[email protected]
+    # Prevent duplicate workflow executions for pull_request (PR) and pull_request_target (PRT) events.
+    # Both PR and PRT will be triggered for the same pull request, whether it is internal or from a fork.
+    # This condition will prevent the workflow from running twice for the same pull request while
+    # still allowing it to run for all other event types.
+    if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
+    secrets: inherit
+    with:
+      machine: jetson-nano
+      device-repo: balena-os/balena-jetson
+      device-repo-ref: master
+      # Pin to the current commit
+      meta-balena-ref: ${{ github.sha }}
+      # Don't deploy any artifacts for meta-balena build sanity workflows
+      deploy-s3: false
+      deploy-hostapp: false
+      deploy-ami: false

.github/workflows/raspberrypi2.yml

@@ -0,0 +1,38 @@
+name: Raspberry Pi 2
+
+on:
+  # With these triggers the Yocto jobs will run
+  # in parallel with the Flowzone jobs, which is fine for now
+  # and allows us to better control what we want to test and when.
+  # It is expected that Flowzone could fail, but yocto jobs will run.
+  pull_request:
+    branches:
+      - "main"
+      - "master"
+  pull_request_target:
+    branches:
+      - "main"
+      - "master"
+
+jobs:
+  yocto:
+    name: Yocto
+    # FIXME: This workflow has dependencies on scripts in the balena-yocto-scripts repository
+    # which is pinned separately as a submodule in the device repo. Expect some drift but try to retain compatibility.
+    uses: balena-os/balena-yocto-scripts/.github/workflows/[email protected]
+    # Prevent duplicate workflow executions for pull_request (PR) and pull_request_target (PRT) events.
+    # Both PR and PRT will be triggered for the same pull request, whether it is internal or from a fork.
+    # This condition will prevent the workflow from running twice for the same pull request while
+    # still allowing it to run for all other event types.
+    if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
+    secrets: inherit
+    with:
+      machine: raspberrypi2
+      device-repo: balena-os/balena-raspberrypi
+      device-repo-ref: master
+      # Pin to the current commit
+      meta-balena-ref: ${{ github.sha }}
+      # Don't deploy any artifacts for meta-balena build sanity workflows
+      deploy-s3: false
+      deploy-hostapp: false
+      deploy-ami: false