ldraney/DORA
Archived
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Close CFR gap: CI pipeline for pal-e-services #5

New issue
Closed
opened 2026-05-29 12:05:52 +00:00 by ldraney · 1 comment
ldraney commented 2026-05-29 12:05:52 +00:00
Owner
Copy link

Type

Feature

Lineage

Standalone — identified as measurement gap in DORA framework.

Repo

forgejo_admin/pal-e-services

User Story

As a platform operator
I want Tier 1 DORA composite in Grafana
So that I know if production pipelines are healthy without digging

Context

pal-e-services deploys via manual tofu apply from laptop. No Woodpecker pipeline means no CFR data in Prometheus — this is a Tier 1 repo with a blind spot. Adding CI closes the last manual-deploy gap in the infra layer.

File Targets

Files the agent should modify or create:

  • .woodpecker.yaml in pal-e-services — new Woodpecker pipeline config
  • Potentially terraform/modules/monitoring/ in pal-e-platform — ServiceMonitor if needed

Acceptance Criteria

  • pal-e-services has a Woodpecker pipeline (plan on PR, apply on merge)
  • Pipeline success/failure events appear in dora_deployments_total
  • CFR for pal-e-services is measurable in Grafana

Test Expectations

  • Integration: merge a test PR and verify pipeline runs
  • Verify dora_deployments_total{repo="pal-e-services"} increments

Constraints

  • Follow the same CI pattern as pal-e-platform (plan on PR, apply on merge)
  • Secrets management for tofu credentials in Woodpecker

Checklist

  • PR opened
  • Tests pass
  • No unrelated changes

Related

  • dora-metrics — project this affects
  • pal-e-platform — CI pattern reference
### Type Feature ### Lineage Standalone — identified as measurement gap in DORA framework. ### Repo `forgejo_admin/pal-e-services` ### User Story As a platform operator I want Tier 1 DORA composite in Grafana So that I know if production pipelines are healthy without digging ### Context pal-e-services deploys via manual `tofu apply` from laptop. No Woodpecker pipeline means no CFR data in Prometheus — this is a Tier 1 repo with a blind spot. Adding CI closes the last manual-deploy gap in the infra layer. ### File Targets Files the agent should modify or create: - `.woodpecker.yaml` in pal-e-services — new Woodpecker pipeline config - Potentially `terraform/modules/monitoring/` in pal-e-platform — ServiceMonitor if needed ### Acceptance Criteria - [ ] pal-e-services has a Woodpecker pipeline (plan on PR, apply on merge) - [ ] Pipeline success/failure events appear in `dora_deployments_total` - [ ] CFR for pal-e-services is measurable in Grafana ### Test Expectations - [ ] Integration: merge a test PR and verify pipeline runs - [ ] Verify `dora_deployments_total{repo="pal-e-services"}` increments ### Constraints - Follow the same CI pattern as pal-e-platform (plan on PR, apply on merge) - Secrets management for tofu credentials in Woodpecker ### Checklist - [ ] PR opened - [ ] Tests pass - [ ] No unrelated changes ### Related - `dora-metrics` — project this affects - `pal-e-platform` — CI pattern reference
ldraney commented 2026-06-13 18:36:14 +00:00
Author
Owner
Copy link

Migrated to ldraney/pal-e-services#116

Migrated to ldraney/pal-e-services#116
Commenting is not possible because the repository is archived.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ldraney/DORA#5
No description provided.