Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use GHA for Intel NUC #1

Merged
merged 1 commit into from
Jul 24, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 0 additions & 17 deletions .github/workflows/build_and_deploy.yml

This file was deleted.

27 changes: 0 additions & 27 deletions .github/workflows/esr.yml

This file was deleted.

29 changes: 0 additions & 29 deletions .github/workflows/flowzone.yml

This file was deleted.

46 changes: 0 additions & 46 deletions .github/workflows/genericx86-64.yml

This file was deleted.

22 changes: 12 additions & 10 deletions .github/workflows/intel-nuc.yml
Original file line number Diff line number Diff line change
@@ -1,10 +1,6 @@
name: Intel NUC

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"
Expand All @@ -13,30 +9,36 @@ on:
branches:
- "main"
- "master"

push:
tags:
- v[0-9]+.[0-9]+.[0-9]+\+?r?e?v?*
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
# Allows you to run this workflow manually from the Actions tab

workflow_dispatch:

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/yocto-build-deploy.yml@v1.25.3
# Pin the workflow to a specific commit to prevent unexpected changes while
# I am learning.
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@v1.25.10
# 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.
# - internal PR (true == true) ok
# - internal PRT (true != false) skip
# - fork PR (false != true) skip
# - fork PRT (false == false) ok
# - push (false == false) ok
# - workflow_dispatch (false == false) ok
# - any trigger other than PR/PRT (false == false) ok
if: (github.event.pull_request.head.repo.full_name == github.repository) == (github.event_name == 'pull_request')
secrets: inherit
with:
machine: genericx86-64
# Needed for testing - defaults to production
environment: balena-staging.com
# Use autokit workers for testing and run on free hosted runners
test_matrix: >
{
"test_suite": ["os","cloud","hup"],
Expand Down
Loading