kjh2064
5c94564c9f
로컬 워크스페이스에서 Gitea Actions를 검증·디스패치할 수 있는 GITEA_TOKEN_HOME API 토큰 계약과, Synology에서 act_runner를 기동하는 스크립트를 추가한다. - validate_gitea_token_home_v1.py: 저장소 메타데이터 조회, 워크플로 접근 확인, workflow_dispatch 트리거 + 최신 실행 결과 폴링 - start_act_runner_synology.sh: Synology 환경에서 act_runner 기동 - setup_act_runner.sh: 기동 절차 갱신
1.5 KiB
1.5 KiB
GITEA_TOKEN_HOME Runbook
1. Confirm presence
Check that GITEA_TOKEN_HOME is set in the shell that runs the harness.
2. Validate read-only access
python tools/validate_gitea_token_home_v1.py
Expected:
gate = PASS- repo access works
- workflow metadata is readable
3. Dispatch smoke test
python tools/validate_gitea_token_home_v1.py --dispatch --workflow kis_data_collection.yml --ref main
Expected:
- dispatch returns
204or201 - latest run is visible in the API
- run status becomes visible in the response payload
4. If it fails
GITEA_TOKEN_HOME missing or empty: environment is not configured401 Unauthorized: token is wrong or lacks repo scope404 Not Found: repo or workflow path mismatchlatest_run_missing: dispatch accepted, but run listing lagged behindqueuedor longin_progress: runner is busy or the job is waiting for the self-hosted runner slot
5. Evidence to capture
- Harness JSON output
- Workflow run URL
- Failing step name if the dispatched run fails
- Runner status from the API if the job stays queued
Current run 161 finding
Checkout Codefailed before Python started.- The repository checkout did not contain
GatherTradingData.json. - This means the next fix is not token-related; it is seed-file availability at workflow runtime.
- The workflow is now updated to regenerate the JSON from
GatherTradingData.xlsxwhen possible and to fail with explicit recovery instructions when both are missing.