You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For flowing code between the VMR and the individual repositories, we will utilize the same mechanism as for current dependency flow - builds, channels and subscriptions.
.NET developers will create subscriptions between the repos and the VMR of a special kind denoting that code will be flown too and these will then be triggered/processed by the Maestro++ service which will in turn call the .NET Product Construction Service.
Goal
To get the above working, we need to extend the current model with the new code flow metadata and teach darc to manage these new code flow subscriptions.
tkapin
changed the title
Extend Maestro++ subscription model with code flow capabilities
Extend Maestro++ subscription model with code flow capabilities
Feb 15, 2024
Context
For flowing code between the VMR and the individual repositories, we will utilize the same mechanism as for current dependency flow - builds, channels and subscriptions.
.NET developers will create subscriptions between the repos and the VMR of a special kind denoting that code will be flown too and these will then be triggered/processed by the
Maestro++
service which will in turn call the.NET Product Construction Service
.Goal
To get the above working, we need to extend the current model with the new code flow metadata and teach
darc
to manage these new code flow subscriptions.Work Items
darc
commands #3255The text was updated successfully, but these errors were encountered: