Skip to content

Commit 98d799c

Browse files
Merge pull request #80 from paritytech/fix/e2e-local-ipfs-init
fix(tools): ipfs init in isolated HOME so e2e-local.sh runs deploy tests
2 parents c9ce102 + 25c51e9 commit 98d799c

1 file changed

Lines changed: 9 additions & 0 deletions

File tree

tools/e2e-local.sh

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,15 @@ ISOLATED_HOME="$(mktemp -d -t dot-e2e-home-XXXXXX)"
3535
trap 'rm -rf "$ISOLATED_HOME"' EXIT
3636
export HOME="$ISOLATED_HOME"
3737

38+
# Bootstrap a fresh IPFS repo in the isolated HOME. The deploy tests shell
39+
# out to `ipfs add` (via bulletin-deploy's Kubo path), and IPFS resolves the
40+
# repo location from `$HOME/.ipfs` by default. Without this, the deploy
41+
# tests fail with "no IPFS repo found in <isolated home>/.ipfs". CI does
42+
# the same thing in the workflow's `ipfs init --profile=test` step.
43+
if command -v ipfs >/dev/null 2>&1; then
44+
ipfs init --profile=test >/dev/null 2>&1 || true
45+
fi
46+
3847
echo "→ TEST_TEMPLATE_DOMAIN $TEST_TEMPLATE_DOMAIN"
3948
echo "→ TEST_TEMPLATE_REPO $TEST_TEMPLATE_REPO"
4049
echo "→ DOT_DEPLOY_VERBOSE $DOT_DEPLOY_VERBOSE"

0 commit comments

Comments
 (0)