Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stable shipping assets should go to isolated feeds only if they are actually stable #15531

Open
mmitche opened this issue Feb 13, 2025 · 0 comments
Assignees

Comments

@mmitche
Copy link
Member

mmitche commented Feb 13, 2025

Today, if a build is marked as stable, we create isolated feeds for the shipping outputs. Then, any shipping output ends up on those feeds. The VMR has ocassional stable assets from some repos. We don't want these always pushed to isolated feeds, since that will make maestro updates via backflow (or forward) messy.

Instead, individual assets that are marked stable should only go to the isolated feed. To do this, we should propagate IsStable to individual assets, rather than on the whole build itself.

@mmitche mmitche self-assigned this Feb 13, 2025
@mmitche mmitche converted this from a draft issue Feb 13, 2025
@mmitche mmitche moved this from Ready to In Progress in .NET Unified Build Feb 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant