github: deploy mcs verification manifest

Deploy the MCS verification manifest for versions that have no MCS
preprocess differences. These may be different from non-MCS preprocess
outcomes, and since the MCS verification is on a branch, we can deploy
it separately.

Signed-off-by: Gerwin Klein <gerwin.klein@proofcraft.systems>
This commit is contained in:
Gerwin Klein
2025-04-01 19:05:56 +11:00
parent 29803c51ca
commit 38e889da3b

View File

@@ -32,12 +32,25 @@ jobs:
strategy:
matrix:
arch: [ARM, ARM_HYP, AARCH64, RISCV64, X64]
# no MCS here, auto-updating mcs.xml should be a separate job.
# no MCS here, see separate preprocess-mcs.
steps:
- uses: seL4/ci-actions/preprocess@master
with:
L4V_ARCH: ${{ matrix.arch }}
preprocess-mcs:
name: Preprocess (MCS)
needs: code
runs-on: ubuntu-latest
strategy:
matrix:
arch: [RISCV64]
steps:
- uses: seL4/ci-actions/preprocess@master
with:
L4V_ARCH: ${{ matrix.arch }}
L4V_FEATURES: "MCS"
deploy:
name: Deploy manifest
needs: [code, preprocess]
@@ -50,3 +63,17 @@ jobs:
preprocess: 'true'
env:
GH_SSH: ${{ secrets.CI_SSH }}
deploy-mcs:
name: Deploy MCS manifest
needs: [code, preprocess-mcs]
if: ${{ github.repository_owner == 'seL4' }}
runs-on: ubuntu-22.04
steps:
- uses: seL4/ci-actions/l4v-deploy@master
with:
xml: ${{ needs.code.outputs.xml }}
preprocess: 'true'
manifest: mcs-devel.xml
env:
GH_SSH: ${{ secrets.CI_SSH }}