fix(cicd): E2E-CI ohne Port-Konflikte, PR-Checks immer, strip-ports.mjs, run-rm #238
No reviewers
Labels
No labels
component/backend
component/docs
component/e2e
component/frontend
component/infra
component/keycloak
prio/high
prio/low
prio/medium
type/bug
type/chore
type/feature
type/refactor
type/test
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
WompSchmiede/FamilienFeierPlaner!238
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/e2e-keycloak-port"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
E2E-CI-Pipeline fuer Gitea-Actions-Runner repariert:
strip-ports.mjsentfernt Ports aus docker-compose.yml → keine Port-Konfliktedocker compose exec -T backend-api node -e fetch()(kein curl noetig)run --rm e2e-runner(Container ohne Daemon)ENCRYPTION_KEYstatisch inenv:(64 hex chars)ci-backend.yml/ci-frontend.yml:pull_requestohnepaths:→ Checks laufen immer als Status-Checks fuer Branch-Protectionpush mainbehaeltpaths:-FilterRefs #212
4234e7e6914f5b44c2f3