Onboard rocm-examples for subscription service (Phase 2 B.2)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 16
Description
Phase: 2B
Labels: quartz, phase-2, onboarding
Blocked by: Phase 2 B1 (test repo validation passed), Phase 2 A2 (onboarding docs ready)
Context
After the push notification flow is validated on the test repository, onboard the
first real downstream subscriber (rocm-examples). This involves coordinating with
the rocm-examples maintainers, installing Quartz Conveyor, and adding their entry
to config/subscriber.yml.
Reference: RFC-0011 (ROCm/TheRock#3728 / docs/rfcs/RFC0011-Quartz-CICD-Datahub.md in ROCm/TheRock once merged) — Phase 2, Section B.
Tasks
- Coordinate with rocm-examples maintainers: share
docs/push-subscription.md
and agree on which events and pipelines they subscribe to - rocm-examples installs Quartz Conveyor app in their repository
- rocm-examples adds
templates/subscriber-push.yml(or equivalent) to their
repository - Open onboarding PR to
ROCm/quartzadding rocm-examples to
config/subscriber.ymlusing the.github/PULL_REQUEST_TEMPLATE/new-subscriber.md
template - Validate end-to-end with a real TheRock nightly trigger
Notes
- rocm-examples is the starting point; additional subscribers follow the same process
independently and do not need a dedicated issue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with docs/push-subscription.md and the subscriber onboarding template at .github/PULL_REQUEST_TEMPLATE/new-subscriber.md, then review config/subscriber.yml. Coordinate the listed event and pipeline choices with rocm-examples, confirm their Conveyor installation and subscriber-push.yml, open the onboarding PR, and validate it with a real TheRock nightly trigger.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100