Started by an SCM change8b3eac39728b98ecd0a24508a1d160383aec84a2fb3eac39728b98ecd0a24508a1d160383aec84a2frefs/remotes/origin/mainb3eac39728b98ecd0a24508a1d160383aec84a2fb3eac39728b98ecd0a24508a1d160383aec84a2frefs/remotes/origin/mainb3eac39728b98ecd0a24508a1d160383aec84a2fb3eac39728b98ecd0a24508a1d160383aec84a2frefs/remotes/origin/mainhttps://github.com/younex1/deploy-younex-web.gitfalseb3eac39 paas: port conflict detection for create/auto-assign + health-gate port #81344412371paas-platform #88false85819SUCCESS1791496147812https://jenkins.younex.de/job/paas-platform/8/- bin/paasb3eac39728b98ecd0a24508a1d160383aec84a2f1791496068000https://jenkins.younex.de/user/infoinfoinfo@logyou.depaas: port conflict detection for create/auto-assign + health-gate port guard on deploy
Every app owns PORT and PORT+1000 (health gate). 'paas create --port' now refuses a port
that another app uses as PORT or gate port, the panel port, or anything already bound on
the host, and auto-assignment skips those too; 'paas deploy' refuses to gate on a port
another process answers on. Found when kredible-sw was created on logship-landing's port
and the gate health-checked the wrong app.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-10-08 23:47:48 +0200b3eac39728b98ecd0a24508a1d160383aec84a2fpaas: port conflict detection for create/auto-assign + health-gate port guard on deployeditbin/paas
githttps://jenkins.younex.de/user/infoinfofalse9https://jenkins.younex.de/job/paas-platform/9/7https://jenkins.younex.de/job/paas-platform/7/