The forgejo-runner on srv-102v advertises labels `incus:host,self-hosted:host`, so jobs pinned to `ubuntu-latest` matched no runner and exited in 0s. - ci.yml / security-scan.yml / trivy-fs.yml: runs-on → [self-hosted, incus] - e2e.yml / go-fuzz.yml / loadtest.yml: same migration AND gate triggers to workflow_dispatch only (push/pull_request/schedule commented out) — single self-hosted runner, heavy suites would block the queue. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
24 lines
656 B
YAML
24 lines
656 B
YAML
name: Trivy Filesystem Scan
|
|
|
|
on:
|
|
pull_request:
|
|
branches: [main]
|
|
workflow_dispatch:
|
|
|
|
env:
|
|
GIT_SSL_NO_VERIFY: "true"
|
|
|
|
jobs:
|
|
trivy-scan:
|
|
name: Trivy FS Scan
|
|
runs-on: [self-hosted, incus]
|
|
steps:
|
|
- uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
|
|
|
|
- name: Install Trivy
|
|
run: |
|
|
wget -qO- https://github.com/aquasecurity/trivy/releases/download/v0.58.1/trivy_0.58.1_Linux-64bit.tar.gz | tar xz
|
|
chmod +x trivy
|
|
|
|
- name: Scan filesystem
|
|
run: ./trivy fs --severity HIGH,CRITICAL --exit-code 1 .
|