Skip to content

Actually try a series22 build #2

Actually try a series22 build

Actually try a series22 build #2

Workflow file for this run

on: [push, pull_request]
jobs:
build_job:
# The host should always be linux
runs-on: ubuntu-22.04
name: Build on ubuntu22.04 armhf
# Run steps on a matrix of 4 arch/distro combinations
steps:
- uses: actions/checkout@v4
fetch-depth: 0

Check failure on line 12 in .github/workflows/armhf_lxd.yaml

View workflow run for this annotation

GitHub Actions / .github/workflows/armhf_lxd.yaml

Invalid workflow file

The workflow is not valid. .github/workflows/armhf_lxd.yaml (Line: 12, Col: 9): Unexpected value 'fetch-depth' .github/workflows/armhf_lxd.yaml (Line: 54, Col: 9): Unexpected value 'path'
- uses: uraimo/run-on-arch-action@v2
name: Build artifact
id: build
with:
arch: armv7
distro: ubuntu22.04
# Not required, but speeds up builds
#githubToken: ${{ github.token }}
# Mount the artifacts directory as /artifacts in the container
dockerRunArgs: |
--volume "$GITHUB_WORKSPACE/checkbox:/checkbox"
# The shell to run commands with in the container
shell: /bin/bash
# Install some dependencies in the container. This speeds up builds if
# you are also using githubToken. Any dependencies installed here will
# be part of the container image that gets cached, so subsequent
# builds don't have to re-install them. The image layer is cached
# publicly in your project's package repository, so it is vital that
# no secrets are present in the container state or logs.
install: |
sudo snap install lxd snapcraft
sudo lxd init --auto
# Produce a binary artifact and place it in the mounted volume
run: |
cd /checkbox/checkbox-core-snap/
./prepare.sh series22
cd series22
sudo snapcraft --use-lxd
- name: Show the artifact
# Items placed in /artifacts in the container will be in
# ${PWD}/artifacts on the host.
run: |
ls checkbox/checkbox-core-snap/series22
- uses: actions/upload-artifact@v4
path: checkbox-core-snap/series22/*.snap