mirror of
https://github.com/aljazceru/kata-containers.git
synced 2025-12-26 10:34:24 +01:00
`snap`/`snapcraft` seems to have changed recently. Since `snap` auto-updates all `snap` packages and since we use the `snapcraft` `snap` for building snaps, this is impacting all our CI jobs which now show: ``` Installing Snapcraft for Linux… snapcraft 7.0.4 from Canonical* installed Run snapcraft -d snap --destructive-mode Usage: snapcraft [options] command [args]... Try 'snapcraft pack -h' for help. Error: unrecognized arguments: -d Error: Process completed with exit code 1. ``` Move the debug option to make it a sub-command (long) option to resolve this issue. Fixes: #4457. Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
28 lines
694 B
YAML
28 lines
694 B
YAML
name: snap CI
|
|
on:
|
|
pull_request:
|
|
types:
|
|
- opened
|
|
- synchronize
|
|
- reopened
|
|
- edited
|
|
|
|
jobs:
|
|
test:
|
|
runs-on: ubuntu-20.04
|
|
steps:
|
|
- name: Check out
|
|
if: ${{ !contains(github.event.pull_request.labels.*.name, 'force-skip-ci') }}
|
|
uses: actions/checkout@v2
|
|
with:
|
|
fetch-depth: 0
|
|
|
|
- name: Install Snapcraft
|
|
if: ${{ !contains(github.event.pull_request.labels.*.name, 'force-skip-ci') }}
|
|
uses: samuelmeuli/action-snapcraft@v1
|
|
|
|
- name: Build snap
|
|
if: ${{ !contains(github.event.pull_request.labels.*.name, 'force-skip-ci') }}
|
|
run: |
|
|
snapcraft snap --debug --destructive-mode
|