22 lines
1.2 KiB
Markdown
22 lines
1.2 KiB
Markdown
# Delivery feedback
|
|
|
|
`maidn app onboard` adds source-owned Tekton tasks that update one marked
|
|
Forgejo pull-request comment. The comment contains only the verified preview
|
|
URL, a redacted task-status summary, and the PipelineRun name. Set the optional
|
|
`delivery.tektonDashboardUrl` to a credential-free HTTPS Tekton Dashboard
|
|
origin to add a PipelineRun link.
|
|
|
|
Before enabling delivery feedback, create the separate Forgejo token with
|
|
`bootstrap --config <private-bootstrap-config> --create-forgejo-delivery-status-token`.
|
|
It creates or reuses `maidn-delivery-status` at
|
|
`cicd/forgejo-delivery-status.token`, with only `write:issue` and
|
|
`write:repository` for pull-request comments and commit statuses. It does not
|
|
reuse the Git clone/push token. The generated task never prints the token or
|
|
Forgejo API responses.
|
|
|
|
Preview and staging feedback waits up to ten minutes for the app Deployment
|
|
and HTTPRoute, then performs a bounded HTTPS check. A production event reports
|
|
the manifest-repository promotion PR; it does not claim a production deploy.
|
|
The chart must name both resources after `delivery.appName`; the HTTPRoute's
|
|
first hostname must be the public HTTPS preview/staging URL.
|