clone

a personal forge on plain git: static pages, stacked-diff reviews, signed local ci, repo sites and releases

Pass the scenarios in the container, as root #5

9 commits: 6 unchanged, 1 rewritten, 2 added.

4 unchanged commits
unchanged 8ef01c6 → 396feb7 Write a Caddyfile without FORGE_BASE_URL under dash too
unchanged 0bec909 → 18f6a75 Make scenarios' HTTP requests with Node, not curl
unchanged 6641d3b → 982bfb4 Read file modes in scenarios the same with GNU and BSD stat
unchanged 80fabe5 → f1bc047 Expect a release's publisher to be whoever runs the scenarios
rewritten a9984f2 → 79c9c92 Let a restore run as root hand the forge to git in scenarios tests only
@@ Commit message
caches root's builds had filled. lib.sh opens the directory to git when
it runs as root and git exists, and restore_into restores into a new
forge with its pages and caches inside it, as a new host has, so git
- owns them once forge restore has chowned it. The six scenarios that
+ owns them once forge restore has chowned it. The seven scenarios that
restore use it. Nothing changes for a normal user: restore finishes as
them, as before.
@@ test/scenarios/private-backup.sh: exists "$st/dami/open.git/git-daemon-export-ok
exists "$r/dami/open.git/git-daemon-export-ok"
eq "$(cat "$r/dami/secret.git/forge/readers")" ana
+ ## test/scenarios/release-private-store-backup.sh ##
+@@ test/scenarios/release-private-store-backup.sh: missing "$st/.forge/store"
+ exists "$st/dami/secret.git/HEAD"
+
+ r=$T/restored
+-ok env FORGE_ROOT="$r" FORGE_WWW="$r/.forge/www" FORGE_CACHE="$T/cache2" "$FORGE" restore --from "$st"
++ok restore_into "$r" --from "$st"
+ inode() { ls -i "$1" | awk '{ print $1 }'; }
+ dl=dami/secret/releases/download
+ ok cmp "$T/f/tool" "$r/.forge/private/store/$secret/tool"
+
## test/scenarios/release-restore.sh ##
@@ test/scenarios/release-restore.sh: ok forge backup --dry-run
st=$FORGE_ROOT/.forge/backup/stage
2 unchanged commits
unchanged 25881e2 → 2f1c626 Run scenarios' Caddy with the container's Caddy 2.6 too
unchanged 39fdebe → e28b6f3 Run the scenarios in the forge's container, as root
added 0a05b71 Type-check the scenarios' TypeScript helpers too
added 8e63d4d Run the scenarios in the container from CI, when asked