hmk/haemka.de
1
0
Fork 0
Code Issues Actions Activity

Force IPv4 for git.haemka.in SSH connections too

Browse Source 
Missed two spots: the git.haemka.in keyscan and the submodule fetch's
GIT_SSH_COMMAND. If git.haemka.in's DNS answer includes an AAAA record
(depends on which resolver the runner hits), these hit the same no
IPv6 route issue intermittently, explaining the flaky failures.
This commit is contained in:
haemka
2026-08-13 15:35:16 +00:00
parent 02d660416a
commit 84ef10b88e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.gitea/workflows/build-deploy.yml
+2 -2
View File
@@ -31,7 +31,7 @@ jobs:
mkdir -p ~/.ssh mkdir -p ~/.ssh
printf '%s\n' "$DEPLOY_SSH_KEY" > ~/.ssh/deploy_key printf '%s\n' "$DEPLOY_SSH_KEY" > ~/.ssh/deploy_key
chmod 600 ~/.ssh/deploy_key chmod 600 ~/.ssh/deploy_key
ssh-keyscan -H git.haemka.in >> ~/.ssh/known_hosts ssh-keyscan -4 -H git.haemka.in >> ~/.ssh/known_hosts
ssh-keyscan -4 -H -p "${DEPLOY_PORT:-22}" "$DEPLOY_HOST" >> ~/.ssh/known_hosts ssh-keyscan -4 -H -p "${DEPLOY_PORT:-22}" "$DEPLOY_HOST" >> ~/.ssh/known_hosts
- name: Fetch theme submodule - name: Fetch theme submodule
@@ -40,7 +40,7 @@ jobs:
# so it's fetched over SSH with the deploy key instead of needing a # so it's fetched over SSH with the deploy key instead of needing a
# token with access to both repos. # token with access to both repos.
git config submodule.themes/latex.url git@git.haemka.in:hmk/pelican-latex.git git config submodule.themes/latex.url git@git.haemka.in:hmk/pelican-latex.git
GIT_SSH_COMMAND="ssh -i ~/.ssh/deploy_key -o StrictHostKeyChecking=yes" \ GIT_SSH_COMMAND="ssh -4 -i ~/.ssh/deploy_key -o StrictHostKeyChecking=yes" \
git submodule update --init --recursive git submodule update --init --recursive
- name: Install Python dependencies - name: Install Python dependencies