Skip to content

Commit

Permalink
Use workflow branch ryan/cleanup and clean up inputs
Browse files Browse the repository at this point in the history
Signed-off-by: Kyle Harding <[email protected]>
  • Loading branch information
klutchell committed Aug 15, 2024
1 parent a723f5a commit f9a4ec7
Show file tree
Hide file tree
Showing 10 changed files with 130 additions and 140 deletions.
27 changes: 13 additions & 14 deletions .github/workflows/beaglebone.yml
Original file line number Diff line number Diff line change
@@ -1,38 +1,37 @@
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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
27 changes: 13 additions & 14 deletions .github/workflows/generic-aarch64.yml
Original file line number Diff line number Diff line change
@@ -1,41 +1,40 @@
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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: 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: >
Expand Down
27 changes: 13 additions & 14 deletions .github/workflows/generic-amd64.yml
Original file line number Diff line number Diff line change
@@ -1,41 +1,40 @@
name: Generic x86_64 (GPT)

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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
machine: generic-amd64
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
# Use QEMU workers for testing and run cloud suite against balenaCloud production
test_matrix: >
{
Expand Down
27 changes: 13 additions & 14 deletions .github/workflows/genericx86-64-ext.yml
Original file line number Diff line number Diff line change
@@ -1,41 +1,40 @@
name: Generic x86_64 (legacy MBR)

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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
machine: genericx86-64-ext
device-repo: balena-os/balena-intel
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
# Use QEMU workers for testing and run cloud suite against balenaCloud production
test_matrix: >
{
Expand Down
27 changes: 13 additions & 14 deletions .github/workflows/genericx86-64.yml
Original file line number Diff line number Diff line change
@@ -1,38 +1,37 @@
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"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
machine: genericx86-64
device-repo: balena-os/balena-intel
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
27 changes: 13 additions & 14 deletions .github/workflows/jetson-nano.yml
Original file line number Diff line number Diff line change
@@ -1,38 +1,37 @@
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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
27 changes: 13 additions & 14 deletions .github/workflows/raspberrypi2.yml
Original file line number Diff line number Diff line change
@@ -1,38 +1,37 @@
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"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+
pull_request_target:
branches:
- "main"
- "master"
- main
- master
# ESR branches glob pattern
- v20[0-9][0-9].[0-1]?[1470].[0-9]+

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@d59fac4cce1dcff0b423ac97aeccbd7f4486b9c2 # v1.25.8
uses: balena-os/balena-yocto-scripts/.github/workflows/yocto-build-deploy.yml@ryan/cleanup
# 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:
# Needed for testing - defaults to production
deploy-environment: balena-staging.com
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
# FIXME: we need to disable draft deploys as well!
finalize-on-push-if-tests-passed: false
Loading

0 comments on commit f9a4ec7

Please sign in to comment.