DarkHelm.org/plex-playlist
Public Access
4
0
Fork 0
Code Issues 62 Pull Requests 1 Actions 9 Packages Projects 1 Releases Wiki Activity

EPIC: Separate deployable runtime images from CI validation environments #66

New Issue
Open
opened 2026-06-17 19:33:30 -04:00 by darkhelm · 0 comments
darkhelm commented 2026-06-17 19:33:30 -04:00
Owner
Copy Link

Summary

Establish a CI/CD architecture where deployable backend and frontend images are minimal runtime artifacts, while checks and tests run in dedicated validation environments. Promote only validated immutable digests to staging.

Problem

Current CI and validation concerns are coupled to a CI-focused image. We need a clearer boundary between:

  • deployable runtime artifacts
  • CI tooling and validation environments

This will reduce release-image complexity, improve deploy confidence, and make digest promotion explicit.

Goals

  1. Keep deployable backend and frontend images minimal and production-focused.
  2. Run source-level checks independently of deployable images.
  3. Run post-build integration and E2E checks against running runtime containers.
  4. Promote immutable validated digests only.
  5. Avoid rebuilding artifacts after validation passes.

Non-Goals

  1. Full production rollout automation in this epic.
  2. Re-architecting app behavior or feature logic.
  3. Replacing current test frameworks.

Acceptance Criteria

  1. Backend and frontend runtime images are independently buildable and deployable.
  2. Source-level checks run in their own lane and gate downstream promotion.
  3. Integration and E2E validation run against started runtime containers over network.
  4. Staging deployment consumes immutable digests produced by validated builds.
  5. No post-validation rebuild occurs in promotion path.

Subtickets

1. Define and lock minimal deployable backend/frontend image requirements.
2. Split CI tooling environment from deployable runtime images.
3. Establish source-level fast-check lane.
4. Add post-build black-box integration tests against runtime containers.
5. Run browser E2E from dedicated runner image against runtime services.
6. Implement digest-based artifact promotion gates.
7. Wire staging deployment to validated runtime digests only.
8. Add observability and rollback for staged digest deployments.

Dependencies

None.

Definition of Done

All subtickets are complete and acceptance criteria are met end-to-end.

## Summary Establish a CI/CD architecture where deployable backend and frontend images are minimal runtime artifacts, while checks and tests run in dedicated validation environments. Promote only validated immutable digests to staging. ## Problem Current CI and validation concerns are coupled to a CI-focused image. We need a clearer boundary between: - deployable runtime artifacts - CI tooling and validation environments This will reduce release-image complexity, improve deploy confidence, and make digest promotion explicit. ## Goals 1. Keep deployable backend and frontend images minimal and production-focused. 2. Run source-level checks independently of deployable images. 3. Run post-build integration and E2E checks against running runtime containers. 4. Promote immutable validated digests only. 5. Avoid rebuilding artifacts after validation passes. ## Non-Goals 1. Full production rollout automation in this epic. 2. Re-architecting app behavior or feature logic. 3. Replacing current test frameworks. ## Acceptance Criteria 1. Backend and frontend runtime images are independently buildable and deployable. 2. Source-level checks run in their own lane and gate downstream promotion. 3. Integration and E2E validation run against started runtime containers over network. 4. Staging deployment consumes immutable digests produced by validated builds. 5. No post-validation rebuild occurs in promotion path. ## Subtickets [1. Define and lock minimal deployable backend/frontend image requirements.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/58) [2. Split CI tooling environment from deployable runtime images.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/59) [3. Establish source-level fast-check lane.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/60) [4. Add post-build black-box integration tests against runtime containers.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/61) [5. Run browser E2E from dedicated runner image against runtime services.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/62) [6. Implement digest-based artifact promotion gates.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/63) [7. Wire staging deployment to validated runtime digests only.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/64) [8. Add observability and rollback for staged digest deployments.](https://dogar.darkhelm.org/DarkHelm.org/plex-playlist/issues/65) ## Dependencies None. ## Definition of Done All subtickets are complete and acceptance criteria are met end-to-end.
darkhelm added a new dependency 2026-06-17 19:36:07 -04:00
#60 TASK: Establish source-level fast-check lane
darkhelm added a new dependency 2026-06-17 19:38:56 -04:00
#63 TASK: Implement digest-based artifact promotion gates
darkhelm changed title from Epic: Separate deployable runtime images from CI validation environments to EPIC: Separate deployable runtime images from CI validation environments 2026-06-18 11:55:30 -04:00
darkhelm added the epic label 2026-06-18 11:56:31 -04:00
darkhelm added this to the META: Plex Dynamic Realtime Playlist Generator v1 milestone 2026-06-18 11:58:32 -04:00
darkhelm added this to the Main Project Board project 2026-06-18 11:58:40 -04:00
darkhelm self-assigned this 2026-06-18 11:59:25 -04:00
darkhelm added the afk label 2026-06-18 12:05:02 -04:00
darkhelm moved this to To Do in Main Project Board on 2026-06-19 09:24:27 -04:00
darkhelm moved this to In Progress in Main Project Board on 2026-06-19 09:24:31 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
afk
Autonomous-friendly issue
 algorithm
Selection logic
 api
API contract
 backend
Backend related
 database
Database related
 devex
Developer experience
 docs
Documentation
 epic
Top-level planning item
 frontend
Frontend related
 hitl
Requires human-in-the-loop decision
 ingestion
Ingestion/sync
 ops
Operations
 performance
Performance
 realtime
Realtime/eventing
 release
Release readiness
 security
Security
 task
Implementation ticket
 testing
Testing
 ui
UI/UX
No Label afk epic
Milestone
No items
No Milestone META: Plex Dynamic Realtime Playlist Generator v1
Projects
Clear projects
No project Main Project Board
Assignees
Clear assignees
copilotcoder darkhelm renovate-bot repository-bot
No Assignees darkhelm
1 Participants
Notifications
Due Date
No due date set.
Depends on
#58 TASK: Define and lock minimal deployable backend/frontend image requirements
DarkHelm.org/plex-playlist
#59 TASK: Split CI tooling environment from deployable runtime images
DarkHelm.org/plex-playlist
#60 TASK: Establish source-level fast-check lane
DarkHelm.org/plex-playlist
#61 TASK: Add post-build black-box integration tests against runtime containers
DarkHelm.org/plex-playlist
#62 TASK: Run browser E2E from dedicated runner image against runtime services
DarkHelm.org/plex-playlist
#63 TASK: Implement digest-based artifact promotion gates
DarkHelm.org/plex-playlist
#64 TASK: Wire staging deployment to validated runtime digests only
DarkHelm.org/plex-playlist
#65 TASK: Add observability and rollback for staged digest deployments
DarkHelm.org/plex-playlist
Reference: DarkHelm.org/plex-playlist#66
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?