waku-org/js-waku
1
0
Fork 0
mirror of https://github.com/waku-org/js-waku.git synced 2025-01-11 21:15:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Buid nim-waku node as separate ci step

Browse Source 
So it's easily visible why a run takes longer and an update of the
submodule does not oddly increase the
test step duration.
This commit is contained in:
Franck Royer 2021-03-19 15:16:50 +11:00
parent 26c1511ee8
commit 1cf60d2615
No known key found for this signature in database
GPG Key ID: A82ED75A8DFC50A4
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
.github/workflows/ci.yml vendored
View File

@ -22,6 +22,7 @@ jobs:
run: cd nim-waku && echo "::set-output name=ref::$(git rev-parse HEAD)" run: cd nim-waku && echo "::set-output name=ref::$(git rev-parse HEAD)"
- name: Cache nim-waku binary - name: Cache nim-waku binary
id: cache-nim-waku
uses: actions/cache@v2 uses: actions/cache@v2
with: with:
path: | path: |
@ -29,6 +30,13 @@ jobs:
./nim-waku/vendor/rln/target/debug ./nim-waku/vendor/rln/target/debug
key: nim-waku-build-v2-${{ steps.nim-waku-head.outputs.ref }} 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 - name: Install bufbuild
uses: mu-io/setup-buf@v1beta uses: mu-io/setup-buf@v1beta
with: with: