homelab/stack
1
0
Fork 0
Code Issues 247 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

Persist coverage badge SVG to stable URL for README embedding #42

New Issue
Closed
opened 2026-03-13 14:33:45 +00:00 by kert · 0 comments
kert commented 2026-03-13 14:33:45 +00:00
Owner
Copy Link

Problem

The coverage badge SVG is generated in the CI container but lost when the container exits. There is no stable URL to embed in README or docs.

Fix

Upload to Gitea's generic package registry after each CI run:

curl -sf -X PUT \
  -H "Authorization: token $GITEA_TOKEN" \
  --upload-file coverage.svg \
  "$GITEA_URL/api/packages/homelab/generic/coverage/latest/badge.svg"

Then in README:

![coverage](https://gitea.homelab.fhirworx.io/api/packages/homelab/generic/coverage/latest/badge.svg)

Use failure: ignore so badge upload failures don't block the pipeline.

Acceptance criteria

  • Badge SVG is uploaded to a stable URL after each CI run
  • Badge URL returns valid SVG with current coverage percentage
  • README displays the badge
## Problem The coverage badge SVG is generated in the CI container but lost when the container exits. There is no stable URL to embed in README or docs. ## Fix Upload to Gitea's generic package registry after each CI run: ```shell curl -sf -X PUT \ -H "Authorization: token $GITEA_TOKEN" \ --upload-file coverage.svg \ "$GITEA_URL/api/packages/homelab/generic/coverage/latest/badge.svg" ``` Then in README: ```markdown ![coverage](https://gitea.homelab.fhirworx.io/api/packages/homelab/generic/coverage/latest/badge.svg) ``` Use `failure: ignore` so badge upload failures don't block the pipeline. ## Acceptance criteria - Badge SVG is uploaded to a stable URL after each CI run - Badge URL returns valid SVG with current coverage percentage - README displays the badge
kert added this to the P9: CI/CD Unification milestone 2026-03-13 14:33:45 +00:00
kert added the quality label 2026-03-13 14:33:45 +00:00
kert closed this issue 2026-03-13 14:48:43 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
api
REST API (FastAPI)
 auth
Authentication and authorization
 bib
Bibliography, Zotero, citations
 ci
CI/CD pipelines and Woodpecker plugins
 cli
CLI commands and UX
 cloud
Cloud provider abstraction (AWS, GCP, Azure, self-hosted)
 config
Configuration and wiring
 data
Data loading, CCLF, BCDA, seeds
 databricks
Databricks jobs and deployment
 docs
Documentation and generated references
 image:api
image:docs
image:mc
image:notebooks
image:zotero
infra
lakehouse
Nessie, Polaris, Trino, Iceberg
 llm
llm module — local RAG over comments + Zotero corpus
 notebooks
marimo notebook errors (auto-filed by nb-watcher/nb-integration)
 packaging
Python packaging, optional deps, build system
 pfs
pipeline
Pipeline execution and validation
 pipeline:ci
pipeline:deploy
pipeline:harden
pipeline:infra-ci
pipeline:rebuild-all
pipeline:release
qpp
quality
Testing, coverage, error handling
 step:build
step:deploy
step:hadolint
step:lint
step:publish
step:scan
step:test
step:validate
styles
Charts, figures, visual theming
 tree
Project directory structure and file organization
No Label quality
Milestone
No items
No Milestone P9: CI/CD Unification
Projects
Clear projects
No project
Assignees
Clear assignees
kert renovate-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: homelab/stack#42
Delete Branch "%!s()"

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?