From 1cf60d2615e1f9f0235eb7255ebfc592175c7647 Mon Sep 17 00:00:00 2001
From: Franck Royer <franck@royer.one>
Date: Fri, 19 Mar 2021 15:16:50 +1100
Subject: [PATCH] Buid nim-waku node as separate ci step

So it's easily visible why a run takes longer and an update of the
submodule does not oddly increase the
test step duration.
---
 .github/workflows/ci.yml | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 6f3f6bd6a2..9b52c88b90 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -22,6 +22,7 @@ jobs:
         run: cd nim-waku && echo "::set-output name=ref::$(git rev-parse HEAD)"
 
       - name: Cache nim-waku binary
+        id: cache-nim-waku
         uses: actions/cache@v2
         with:
           path: |
@@ -29,6 +30,13 @@ jobs:
             ./nim-waku/vendor/rln/target/debug
           key: nim-waku-build-v2-${{ steps.nim-waku-head.outputs.ref }}
 
+        # This would have been done part of npm pretest but it gives better
+        # visibility in the CI if done as a separate step
+      - name: Build wakunode2
+        if: steps.cache-nim-waku.outputs.cache-hit != 'true'
+        shell: bash
+        run: cd nim-waku && make wakunode2
+
       - name: Install bufbuild
         uses: mu-io/setup-buf@v1beta
         with: