https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/Blut24 pipeline: deploys branch blut24 to 192.168.12.80 on every push (mirror of erp-frontend-pipeline-production).erp-frontend-pipeline-blut24erp-frontend-pipeline-blut24erp-frontend-pipeline-blut24erp-frontend-pipeline-blut24https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/trueStarted by GitHub push by younex12e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#2633044639204erp-frontend-pipeline-blut24 #22falsefalse25428SUCCESS1785058600023https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/2/Application-Node-Blut24- public/sw-notifications.jsnuxt.config.tse4c83fed1bf0947a5f232df6c6c76cf9154a3df01785058559000https://jenkins.younex.de/user/infoinfoinfo@younex.deblut24: cache-control for /assets + SW cache rename to blut24-erp-v1
Public brand assets had no Cache-Control, so browsers cached them
heuristically — stale LogShip logos survived the rebrand. 5-min
max-age + ETag revalidation fixes that. SW cache renamed; the deploy
job's per-deploy versioning sed is realigned to the new name (it was
a silent no-op since the source moved to logship-erp-v2).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 11:35:59 +0200e4c83fed1bf0947a5f232df6c6c76cf9154a3df0blut24: cache-control for /assets + SW cache rename to blut24-erp-v1editpublic/sw-notifications.jseditnuxt.config.ts
githttps://jenkins.younex.de/user/infoinfoStarted by GitHub push by younex113572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut243572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut243572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#1645364639204erp-frontend-pipeline-blut24 #11falsefalse15427SUCCESS1785057742058https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/1/Application-Node-Blut24gitblueStarted by GitHub push by younex113572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut243572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut243572cc99e2a37553e76905ed3e2fcaa6572305fb3572cc99e2a37553e76905ed3e2fcaa6572305fbrefs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#1645364639204erp-frontend-pipeline-blut24 #11falsefalse15427SUCCESS1785057742058https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/1/Application-Node-Blut24gitBuild stability: No recent builds failed.icon-health-80plushealth-80plus.png100falsefalseStarted by GitHub push by younex12e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#2633044639204erp-frontend-pipeline-blut24 #22falsefalse25428SUCCESS1785058600023https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/2/Application-Node-Blut24- public/sw-notifications.jsnuxt.config.tse4c83fed1bf0947a5f232df6c6c76cf9154a3df01785058559000https://jenkins.younex.de/user/infoinfoinfo@younex.deblut24: cache-control for /assets + SW cache rename to blut24-erp-v1
Public brand assets had no Cache-Control, so browsers cached them
heuristically — stale LogShip logos survived the rebrand. 5-min
max-age + ETag revalidation fixes that. SW cache renamed; the deploy
job's per-deploy versioning sed is realigned to the new name (it was
a silent no-op since the source moved to logship-erp-v2).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 11:35:59 +0200e4c83fed1bf0947a5f232df6c6c76cf9154a3df0blut24: cache-control for /assets + SW cache rename to blut24-erp-v1editpublic/sw-notifications.jseditnuxt.config.ts
githttps://jenkins.younex.de/user/infoinfoStarted by GitHub push by younex12e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#2633044639204erp-frontend-pipeline-blut24 #22falsefalse25428SUCCESS1785058600023https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/2/Application-Node-Blut24- public/sw-notifications.jsnuxt.config.tse4c83fed1bf0947a5f232df6c6c76cf9154a3df01785058559000https://jenkins.younex.de/user/infoinfoinfo@younex.deblut24: cache-control for /assets + SW cache rename to blut24-erp-v1
Public brand assets had no Cache-Control, so browsers cached them
heuristically — stale LogShip logos survived the rebrand. 5-min
max-age + ETag revalidation fixes that. SW cache renamed; the deploy
job's per-deploy versioning sed is realigned to the new name (it was
a silent no-op since the source moved to logship-erp-v2).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 11:35:59 +0200e4c83fed1bf0947a5f232df6c6c76cf9154a3df0blut24: cache-control for /assets + SW cache rename to blut24-erp-v1editpublic/sw-notifications.jseditnuxt.config.ts
githttps://jenkins.younex.de/user/infoinfoStarted by GitHub push by younex12e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#2633044639204erp-frontend-pipeline-blut24 #22falsefalse25428SUCCESS1785058600023https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/2/Application-Node-Blut24- public/sw-notifications.jsnuxt.config.tse4c83fed1bf0947a5f232df6c6c76cf9154a3df01785058559000https://jenkins.younex.de/user/infoinfoinfo@younex.deblut24: cache-control for /assets + SW cache rename to blut24-erp-v1
Public brand assets had no Cache-Control, so browsers cached them
heuristically — stale LogShip logos survived the rebrand. 5-min
max-age + ETag revalidation fixes that. SW cache renamed; the deploy
job's per-deploy versioning sed is realigned to the new name (it was
a silent no-op since the source moved to logship-erp-v2).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 11:35:59 +0200e4c83fed1bf0947a5f232df6c6c76cf9154a3df0blut24: cache-control for /assets + SW cache rename to blut24-erp-v1editpublic/sw-notifications.jseditnuxt.config.ts
githttps://jenkins.younex.de/user/infoinfoStarted by GitHub push by younex12e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24e4c83fed1bf0947a5f232df6c6c76cf9154a3df0e4c83fed1bf0947a5f232df6c6c76cf9154a3df0refs/remotes/origin/blut24https://github.com/younex1/erp-nuxt-frontend.gitfalse#2633044639204erp-frontend-pipeline-blut24 #22falsefalse25428SUCCESS1785058600023https://jenkins.younex.de/job/erp-frontend-pipeline-blut24/2/Application-Node-Blut24- public/sw-notifications.jsnuxt.config.tse4c83fed1bf0947a5f232df6c6c76cf9154a3df01785058559000https://jenkins.younex.de/user/infoinfoinfo@younex.deblut24: cache-control for /assets + SW cache rename to blut24-erp-v1
Public brand assets had no Cache-Control, so browsers cached them
heuristically — stale LogShip logos survived the rebrand. 5-min
max-age + ETag revalidation fixes that. SW cache renamed; the deploy
job's per-deploy versioning sed is realigned to the new name (it was
a silent no-op since the source moved to logship-erp-v2).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-26 11:35:59 +0200e4c83fed1bf0947a5f232df6c6c76cf9154a3df0blut24: cache-control for /assets + SW cache rename to blut24-erp-v1editpublic/sw-notifications.jseditnuxt.config.ts
githttps://jenkins.younex.de/user/infoinfo3falsefalseapp-agent-blut24hudson.plugins.git.GitSCM--ffdefault