aitbc1
eb5281c55c
Some checks failed
/ audit (push) Failing after 1s
ci-cd / build (push) Failing after 5s
ci / build (push) Failing after 2s
autofix / fix (push) Failing after 2s
security-scanning / audit (push) Failing after 4s
test / test (push) Successful in 2s
ci-cd / deploy (push) Has been skipped
This workflow will show: - Current working directory - User and environment info - Force absolute workspace creation - Repository cloning status - Package.json detection - NPM install attempt This should definitively show what's happening with the runner and whether our fixes are actually being executed.
49 lines
1.5 KiB
YAML
49 lines
1.5 KiB
YAML
name: debug-test
|
|
|
|
on:
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
debug:
|
|
runs-on: debian
|
|
|
|
steps:
|
|
- name: Ultimate debug - show everything
|
|
run: |
|
|
echo "=== ULTIMATE DEBUG ==="
|
|
echo "Current working directory: $(pwd)"
|
|
echo "User: $(whoami)"
|
|
echo "Home: $HOME"
|
|
echo "Node version: $(node --version)"
|
|
echo "NPM version: $(npm --version)"
|
|
|
|
echo "=== FORCE ABSOLUTE WORKSPACE ==="
|
|
rm -rf /opt/gitea-runner/workspace
|
|
mkdir -p /opt/gitea-runner/workspace
|
|
cd /opt/gitea-runner/workspace
|
|
|
|
echo "Workspace directory: $(pwd)"
|
|
echo "Cloning repository..."
|
|
git clone https://gitea.bubuit.net/oib/aitbc.git repo || echo "Clone failed"
|
|
|
|
if [ -d "repo" ]; then
|
|
cd repo
|
|
echo "Repo directory: $(pwd)"
|
|
echo "Files in repo:"
|
|
ls -la
|
|
|
|
if [ -f "package.json" ]; then
|
|
echo "✅ FOUND package.json!"
|
|
echo "Package.json content:"
|
|
head -10 package.json
|
|
echo "=== ATTEMPTING NPM INSTALL ==="
|
|
npm install --legacy-peer-deps
|
|
echo "✅ NPM INSTALL COMPLETED!"
|
|
else
|
|
echo "❌ NO package.json found!"
|
|
find . -name "package.json" 2>/dev/null || echo "No package.json anywhere"
|
|
fi
|
|
else
|
|
echo "❌ Clone failed - no repo directory"
|
|
fi
|