force cmu-onsite runner due to firewall
Nightly build & deploy / build-and-deploy (push) Failing after 5m0s

This commit is contained in:
2026-09-19 01:17:26 -04:00
parent db75d5bfe7
commit c5cf212d7d
2 changed files with 98 additions and 13 deletions
+52 -9
View File
@@ -17,7 +17,12 @@ on:
jobs:
build-and-deploy:
runs-on: ubuntu-latest
# Pinned to the onsite CMU runner. Only a runner registered with the
# "cmu-onsite" label can reach linux.andrew.cmu.edu, so this guarantees the
# deploy runs from inside CMU's network. A cloud/public runner will never
# pick up this job. The runner must be registered in Docker mode so this
# label maps to a Node-capable Debian image (see README).
runs-on: cmu-onsite
env:
# Absolute base URL where the site is served. Used to build the absolute
@@ -49,6 +54,28 @@ jobs:
sudo apt-get update
sudo apt-get install -y lftp
- name: Preflight — check SFTP host reachability
env:
SFTP_HOST: ${{ secrets.SFTP_HOST }}
SFTP_PORT: ${{ secrets.SFTP_PORT }}
run: |
set -uo pipefail
PORT="${SFTP_PORT:-22}"
if [ -z "${SFTP_HOST}" ]; then
echo "::error::SFTP_HOST secret is empty. Set it in Gitea → Settings → Actions → Secrets."
exit 1
fi
echo "Testing TCP reachability of ${SFTP_HOST}:${PORT} ..."
if ! timeout 15 bash -c "cat < /dev/null > /dev/tcp/${SFTP_HOST}/${PORT}" 2>/dev/null; then
echo "::error::Cannot open a TCP connection to ${SFTP_HOST}:${PORT}. This is why lftp reports 'max-retries exceeded'."
echo "Likely causes: wrong SFTP_HOST, wrong port, or the runner cannot reach CMU (needs VPN / on-campus network / firewall allowance)."
exit 1
fi
echo "Host is reachable on ${PORT}. Showing the SSH banner:"
# Non-fatal: just prints what the server advertises (SSH version, etc.)
timeout 10 bash -c "exec 3<>/dev/tcp/${SFTP_HOST}/${PORT}; head -c 200 <&3" 2>/dev/null || true
echo
- name: Upload dist/ via SFTP
env:
SFTP_HOST: ${{ secrets.SFTP_HOST }}
@@ -60,17 +87,33 @@ jobs:
set -euo pipefail
PORT="${SFTP_PORT:-22}"
# Mirror the local dist/ into the remote path.
# -R : reverse mirror (local -> remote)
# --delete : remove remote files no longer present locally
# --verbose : log transferred files
# Host key checking is disabled because CMU's key is not pre-seeded on
# the runner; the connection is still encrypted.
# lftp drives SFTP by shelling out to the system `ssh`. We pass ssh
# options explicitly so this works on a fresh runner against CMU:
# - StrictHostKeyChecking/UserKnownHostsFile: don't fail on an
# unknown host key (the runner has never seen CMU's key).
# - PubkeyAuthentication=no / PreferredAuthentications=password:
# force password auth so ssh doesn't stall trying keys/agent.
# - the KexAlgorithms/HostKeyAlgorithms "+..." lines re-enable
# algorithms some CMU hosts still use that modern OpenSSH disables
# by default (a common cause of a silent connection failure).
#
# `debug 3` prints the negotiation so any remaining failure is visible
# in the job log instead of just "max-retries exceeded".
lftp -c "
set sftp:auto-confirm yes;
set net:max-retries 3;
set net:timeout 20;
set sftp:connect-program 'ssh -a -x \
-o StrictHostKeyChecking=no \
-o UserKnownHostsFile=/dev/null \
-o PubkeyAuthentication=no \
-o PreferredAuthentications=password \
-o KexAlgorithms=+diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1 \
-o HostKeyAlgorithms=+ssh-rsa,ssh-dss';
set net:max-retries 2;
set net:timeout 30;
set net:reconnect-interval-base 5;
debug 3;
open -u '${SFTP_USERNAME}','${SFTP_PASSWORD}' sftp://${SFTP_HOST}:${PORT};
mkdir -f -p '${SFTP_REMOTE_PATH}';
mirror -R --delete --verbose ./dist/ '${SFTP_REMOTE_PATH}';
bye
"