feat: Live-Dashboard auf gitea.slohmaier.com/pages/demo-epb/
Validate / build-test (macos-latest) (push) Failing after 2s
Validate / build-test (ubuntu-latest) (push) Failing after 15s
Validate / build-test (windows-latest) (push) Failing after 15s
Validate / reports (push) Has been skipped

Setup:
- nginx-Vhost gitea.slohmaier.com hat jetzt location /pages/
  fuer statische Files aus /var/www/pages/
- act_runner config.yaml mit -v /var/www/pages:/var/www/pages
  Volume-Mount, damit Jobs aus dem Container schreiben koennen
- /var/www/pages/demo-epb/ writable fuer gitea-runner-User

CI-Deploy:
- validate.yml: bei Push auf main wird das Build ins
  /var/www/pages/demo-epb/ deployt
- release.yml: bei Tag-Push deployt das gesamte Release-Bundle

Live unter https://gitea.slohmaier.com/pages/demo-epb/
This commit is contained in:
Stefan Lohmaier
2026-05-12 02:22:13 -07:00
parent bd744162c5
commit a62acba80b
3 changed files with 37 additions and 0 deletions
+12
View File
@@ -165,6 +165,18 @@ jobs:
echo "Release verfuegbar unter ${GITHUB_SERVER_URL}/${OWNER}/${REPO}/releases/tag/${TAG}"
- name: Deploy zu gitea.slohmaier.com/pages/demo-epb/
run: |
DEPLOY=/var/www/pages/demo-epb
if [ ! -d "$DEPLOY" ]; then
echo "Mount $DEPLOY nicht da — Runner-Config pruefen. Skip."
exit 0
fi
BUNDLE="release/demo-epb-${TAG}"
rm -rf "$DEPLOY"/*
cp -r "$BUNDLE"/. "$DEPLOY/"
echo "https://gitea.slohmaier.com/pages/demo-epb/ updated to ${TAG}"
- name: Upload artifacts (Backup als CI-Artefakt)
uses: actions/upload-artifact@v3
if: always()
+22
View File
@@ -144,3 +144,25 @@ jobs:
with:
name: cppcheck-report
path: build/cppcheck-report.xml
- name: Deploy zu gitea.slohmaier.com/pages/demo-epb/
if: success() && github.ref == 'refs/heads/main'
run: |
DEPLOY=/var/www/pages/demo-epb
if [ ! -d "$DEPLOY" ]; then
echo "Mount $DEPLOY nicht da — Runner-Config pruefen. Skip."
exit 0
fi
mkdir -p "$DEPLOY"/{docs,coverage,traceability,diagrams,api-doc,reports,src,misra/records}
cp build/index.html "$DEPLOY/index.html"
cp -r docs/plaene docs/safety docs/manuals docs/reviews docs/non-conformities "$DEPLOY/docs/"
cp -r build/coverage-html/. "$DEPLOY/coverage/" 2>/dev/null || true
cp -r docs/traceability/. "$DEPLOY/traceability/"
cp -r docs/diagrams/. "$DEPLOY/diagrams/"
cp -r build/api-doc/html/. "$DEPLOY/api-doc/" 2>/dev/null || true
cp build/test-report.html build/test-report.md "$DEPLOY/reports/" 2>/dev/null || true
cp build/cppcheck-report.xml "$DEPLOY/reports/" 2>/dev/null || true
cp src/*.c src/*.h "$DEPLOY/src/"
cp -r src/stubs "$DEPLOY/src/" 2>/dev/null || true
cp -r misra/records/. "$DEPLOY/misra/records/" 2>/dev/null || true
echo "https://gitea.slohmaier.com/pages/demo-epb/ updated"
+3
View File
@@ -2,6 +2,9 @@
Vollständige Demo des [slohmaier Dev Process](https://gitea.slohmaier.com/slohmaier/dev-process) anhand einer EPB-Steuergerät-Software. Zeigt ASPICE 4.0 / ISO 26262-konforme Entwicklung im Monorepo: Anforderungen, Architektur, Code, Tests, Reviews, MISRA, Safety Case, Manuals — alles auf einen Pull-Request-Klick verifizierbar, alles in einem Release-Bundle.
> **🌐 Live-Dashboard:** https://gitea.slohmaier.com/pages/demo-epb/
> Auto-aktualisiert bei jedem Push auf `main` und bei jedem Release-Tag.
> Diese Software ist **bewusst kein Produktivcode** — sie ist die Demonstration des Engineering-Verfahrens. Code-Umfang bewusst klein, Prozess-Tiefe vollständig.
## Was die Demo zeigt