Skip to content

patch: Check if tunnels work without adding keys #305

patch: Check if tunnels work without adding keys

patch: Check if tunnels work without adding keys #305

Workflow file for this run

name: Raspberry Pi 3
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/yocto-build-deploy.yml@0ae0c767ca81526e1f50d702159f5d86ceebee75 # v1.25.24
# 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: raspberrypi3
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

Check failure on line 36 in .github/workflows/raspberrypi3.yml

View workflow run for this annotation

GitHub Actions / Raspberry Pi 3

Invalid workflow file

The workflow is not valid. .github/workflows/raspberrypi3.yml (Line: 36, Col: 18): Invalid input, deploy-s3 is not defined in the referenced workflow. .github/workflows/raspberrypi3.yml (Line: 37, Col: 23): Invalid input, deploy-hostapp is not defined in the referenced workflow.
deploy-hostapp: false
deploy-ami: false