aitbc1
0d83486243
Some checks failed
/ audit (push) Failing after 3s
ci-cd / build (push) Failing after 3s
ci / build (push) Failing after 3s
autofix / fix (push) Failing after 4s
security-scanning / audit (push) Failing after 2s
test / test (push) Failing after 5s
ci-cd / deploy (push) Has been skipped
CRITICAL FIX: Force workspace directory to bypass act_runner host mode issues Runner Configuration Changes: - Set workdir: /opt/gitea-runner/work in gitea-runner/.runner - Created /opt/gitea-runner/work directory - Restarted gitea-runner service to apply configuration - This should fix the hostexecutor vs workspace issue Workflow Nuclear Fix: - Force workspace creation: mkdir -p /opt/gitea-runner/workspace - Manual clone in correct location: cd /opt/gitea-runner/workspace - Bypass all act_runner workspace handling completely - Single-step execution to avoid step isolation issues Updated workflows: - test.yml: Full nuclear fix with verification - audit.yml: Nuclear fix for dependency auditing - fix.yml: Nuclear fix for vulnerability fixing This provides two layers of protection: 1. Runner-level workdir configuration fix 2. Workflow-level manual workspace forcing Expected result: - npm install should now run in /opt/gitea-runner/workspace/repo - package.json should be found and accessible - No more ENOENT errors for missing files
27 lines
602 B
YAML
27 lines
602 B
YAML
name: test
|
|
|
|
on:
|
|
push:
|
|
workflow_dispatch:
|
|
|
|
jobs:
|
|
test:
|
|
runs-on: debian
|
|
|
|
steps:
|
|
- name: Full control execution (nuclear fix)
|
|
run: |
|
|
mkdir -p /opt/gitea-runner/workspace
|
|
cd /opt/gitea-runner/workspace
|
|
rm -rf repo
|
|
git clone https://gitea.bubuit.net/oib/aitbc.git repo
|
|
cd repo
|
|
pwd
|
|
ls -la
|
|
echo "Looking for package.json:"
|
|
ls -la package.json || echo "package.json not found"
|
|
npm install --legacy-peer-deps
|
|
echo "Runner verification:"
|
|
hostname
|
|
whoami
|