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

Playground is being publish from multiple branches, is this the expected behavior? #1922

Open
AlitzelMendez opened this issue Nov 27, 2024 · 0 comments
Labels
eng feature New feature or request triaged:core
Milestone

Comments

@AlitzelMendez
Copy link
Member

As background, on Friday I tried to use the TypeSpec Azure Playground and it was down. @chrisradek quickly identified the reason for the downtime:

  • Someone did a release on a backmerge branch - release/november-2024. That apparently runs the publish playground job. However, the November release didn't include all of the core libraries (I only added those last week), so when the backmerge was released, it broke the playground.

To fix it, Chris ran the pipeline again against main, so the playground got published again in the expected way, and the issue was resolved.

  • Process: Is the expectation that it gets published on every target branch? Can we move this to only get published from main? Or are there considerations like hotfixes that are involved?
  • Alerting: Do we have any alert system for when the playgrounds are down? Is this information centralized? Do we get notified, or do we have a dashboard?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
eng feature New feature or request triaged:core
Projects
None yet
Development

No branches or pull requests

2 participants