Add VMR Repository Onboarding Guide#2635
Conversation
This document provides a step-by-step guide for onboarding new repositories into the VMR (Virtual Monolithic Repository). It covers: - Prerequisites and repository requirements - 6-step onboarding process from source mappings to validation - Proper references to existing detailed VMR documentation - Guidance on handling license and binary validation - Getting help resources The guide follows a one-sentence-per-line convention and focuses on practical, actionable steps rather than duplicating existing detailed documentation.
d889db4 to
2fc3f26
Compare
Co-authored-by: Matt Thalman <[email protected]>
Co-authored-by: Matt Thalman <[email protected]>
Co-authored-by: Přemek Vysoký <[email protected]>
Co-authored-by: Přemek Vysoký <[email protected]>
|
@MichaelSimons if this is a brand new repo (and not arcadified), it would also have to have a build registered in BAR for the subscription to do anything. So I am wondering what kind of repos we're thinking about? But even if you have that repo, it needs to have a build of the SHA you're thinking of ingesting as the subscriptions are build-oriented. The other flow (subscription-less) would be this:
|
I don't see onboarding of a brand new repo before it is onboarded onto arcade and producing builds as something that this document needs to address. I can add a prereq that the repo must have builds registered in BAR. To help clarify, I made this change:
|
Co-authored-by: Matt Thalman <[email protected]>
This document provides a step-by-step guide for onboarding new repositories into the VMR (Virtual Monolithic Repository). It covers:
The guide follows a one-sentence-per-line convention and focuses on practical, actionable steps rather than duplicating existing detailed documentation.