Commit Graph

4 Commits

Author SHA1 Message Date
GSRN
8c9ffb50ce fix: Resolve mvn command not found error in CI workflow
- Replace 'mvn' commands with './mvnw' in CI workflow
- Add chmod +x ./mvnw step to make Maven wrapper executable
- Add cache: maven to Java setup step for better caching
- Update troubleshooting scripts to use correct port 40047
- Update documentation to reflect port change

This fixes the 'mvn: command not found' error by ensuring
all Maven commands use the Maven wrapper (mvnw) which is
included in the project and doesn't require Maven to be
pre-installed on the runner.
2025-09-15 17:16:13 +02:00
GSRN
65c93ae685 fix: Resolve host.docker.internal hostname resolution issue
- Change cache host from 'host.docker.internal' to empty string
- Allow act_runner to auto-detect the correct host IP address
- Update all runner configs: docker, heavy, light, security
- Improve troubleshooting scripts with host IP detection:
  - Linux/macOS: Use ip route, hostname -I, or ifconfig
  - Windows: Use Get-NetIPAddress PowerShell cmdlets
- Update documentation to reflect auto-detection approach

This resolves the 'getaddrinfo ENOTFOUND host.docker.internal' error
by using a more compatible approach that works across different
Docker setups and operating systems.
2025-09-15 17:00:04 +02:00
GSRN
79250ea3ab refactor: Apply cache fixes directly to existing runner configs
Some checks failed
Docker Build and Push / build-and-push (push) Failing after 31s
API Docs (Node.js Express) / test (20) (push) Successful in 3m56s
API Docs (Node.js Express) / test (16) (push) Successful in 4m4s
API Docs (Node.js Express) / test (18) (push) Successful in 4m10s
LabFusion CI/CD Pipeline / api-gateway (push) Failing after 1m22s
LabFusion CI/CD Pipeline / api-docs (push) Successful in 1m2s
API Gateway (Java Spring Boot) / test (17) (push) Failing after 2m39s
API Gateway (Java Spring Boot) / test (21) (push) Failing after 2m45s
API Gateway (Java Spring Boot) / build (push) Has been skipped
API Gateway (Java Spring Boot) / security (push) Has been skipped
LabFusion CI/CD Pipeline / service-adapters (push) Failing after 3m21s
Frontend (React) / test (16) (push) Failing after 1m46s
LabFusion CI/CD Pipeline / frontend (push) Failing after 1m59s
LabFusion CI/CD Pipeline / integration-tests (push) Has been skipped
Frontend (React) / test (18) (push) Failing after 1m50s
Integration Tests / integration-tests (push) Failing after 49s
Integration Tests / performance-tests (push) Has been skipped
Service Adapters (Python FastAPI) / test (3.1) (push) Failing after 1m7s
Frontend (React) / test (20) (push) Failing after 2m30s
Frontend (React) / build (push) Has been skipped
Service Adapters (Python FastAPI) / test (3.11) (push) Failing after 1m43s
Frontend (React) / lighthouse (push) Has been skipped
Service Adapters (Python FastAPI) / test (3.9) (push) Failing after 1m2s
Service Adapters (Python FastAPI) / test (3.12) (push) Failing after 1m43s
Service Adapters (Python FastAPI) / build (push) Has been skipped
API Docs (Node.js Express) / build (push) Successful in 59s
- Update all runner configuration files with cache networking fixes:
  - config_docker.yaml
  - config_heavy.yaml
  - config_light.yaml
  - config_security.yaml
- Remove separate config_cache_fixed.yaml file
- Update troubleshooting scripts to use updated configs
- Update documentation to reference existing config files

All runner configs now have:
- Fixed cache host: host.docker.internal
- Fixed cache port: 44029
- Host networking for better container connectivity

This provides a cleaner approach by updating existing configs
instead of maintaining a separate fixed configuration file.
2025-09-15 16:44:16 +02:00
GSRN
5cecc52572 fix: Resolve cache timeout issues in CI/CD pipelines
- Add fail-on-cache-miss: false to all cache actions in workflows
- Create improved runner configuration (config_cache_fixed.yaml) with:
  - Fixed cache host: host.docker.internal
  - Fixed cache port: 44029
  - Host network mode for better container networking
- Add cache troubleshooting scripts:
  - fix-cache-issues.sh (Linux/macOS)
  - fix-cache-issues.ps1 (Windows)
- Update all workflows: api-gateway, frontend, service-adapters, api-docs, ci

This resolves the 'connect ETIMEDOUT 172.31.0.3:44029' errors by:
1. Making cache failures non-fatal
2. Using proper Docker networking configuration
3. Providing tools to diagnose and fix cache issues
2025-09-15 16:40:52 +02:00