Conditionally compile v2 upgrade module for v1 testing

Concordium · Oct 9, 2023 · ad9c6c8 · ad9c6c8
1 parent f477fdb
commit ad9c6c8
Showing 1 changed file with 6 additions and 1 deletion.
diff --git a/.github/workflows/linter.yml b/.github/workflows/linter.yml
@@ -808,8 +808,8 @@ jobs:
           - examples/signature-verifier
           - examples/transfer-policy-check
           - examples/two-step-transfer
-          - examples/smart-contract-upgrade/contract-version2 # TODO: Will the produced wasm file exist in the v1 run below?
           - examples/smart-contract-upgrade/contract-version1
+          - examples/smart-contract-upgrade/contract-version2
           - examples/offchain-transfers
           - examples/account-signature-checks
 
@@ -830,5 +830,10 @@ jobs:
       - name: Install wasm target and Cargo Concordium
         run: rustup target install wasm32-unknown-unknown && cargo install --locked cargo-concordium
 
+        # The 'smart-contract-upgrade' example has a v1 and v2 contract and the tests in v1 needs the wasm module from v2 for upgrading.
+      - name: Build contract-upgrade version 2 module if needed
+        if: ${{ matrix.crates == 'examples/smart-contract-upgrade/contract-version1' }}
+        run: cargo concordium build --out "examples/smart-contract-upgrade/contract-version2/concordium-out/module.wasm.v1" -- --manifest-path "examples/smart-contract-upgrade/contract-version2/Cargo.toml"
+
       - name: Run cargo concordium test
         run: cargo concordium test --out "${{ matrix.crates }}/concordium-out/module.wasm.v1" -- --manifest-path "${{ matrix.crates }}/Cargo.toml"