A Forgejo-specific OTel trace export action that makes instrumenting CI/CD pipelines easy as pie. 🥧
.forgejo/workflows | ||
.gitignore | ||
.pre-commit-config.yaml | ||
action.yaml | ||
Dockerfile | ||
pyproject.toml | ||
README.md | ||
requirements.txt | ||
tracer.py | ||
uv.lock |
opentelemetry-trace-export-forgejo-action
Handles the export of OTel traces from Forgejo Actions.
Read mirror & usage
If you'd like to use this in your flows, kindly use the Gitlab mirror URL.
Usage
The action pulls action run metadata from non-documented Forgejo APIs and run context data; as long as it runs as the last step, it should capture details from every job in the pipeline.
jobs:
stepA:
...
stepB:
...
export-otel-traces:
...
needs: [stepA, stepB]
steps:
- uses: https://forge.karnov.club/marc/opentelemetry-trace-export-forgejo-action
with:
otlp-endpoint: <GRPC endpoint to send traces to>
otlp-service-name: <Service name to attach to traces>
forgejo-token: <Action-scoped token>
forgejo-base-url: <Base url of the Forgejo instance where the actions are running>
run-id: <Current CI run ID>
repo-name: <Current repository name>