-
Notifications
You must be signed in to change notification settings - Fork 582
Update Release process doc #5159
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
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5159 +/- ##
==========================================
- Coverage 87.28% 86.15% -1.14%
==========================================
Files 59 59
Lines 18086 18086
==========================================
- Hits 15787 15582 -205
- Misses 2299 2504 +205 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
2. When the pipeline passes tests, it'll create a PR. | ||
1. Once the release branch/tag is created, the undock pipeline should run automatically. | ||
- If for some reason there's a problem, the workaround to force a manual re-run by going [here](https://microsoft.visualstudio.com/undock/_git/msquic/tags) (MSFT-only access required) and deleting the tag, and then waiting for the [mirror pipeline](https://microsoft.visualstudio.com/undock/_build?definitionId=134727) (MSFT-only access required) to run automatically re-copy over the tag from GitHub. | ||
- Ideally, it should be "Run Pipeline" [here](https://microsoft.visualstudio.com/undock/_build?definitionId=134439) (MSFT-only access required), scroll down to the **resources tab** and pick the MsQuic release tag of interest, and run it manually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we describe why the ideal process is not the actual process?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
basically there's a bug/limitation of undock pipeline that is forcing the work around today. I wanted to document both what was done today, and what it should be in the future when the bug is fixed/limitation is removed.
Description
Update docs describing the release process