Add source.dot.net stage 1 asset publication #74390
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dotnet-issue-labeler
bot
added
Area-Infrastructure
untriaged
dotnet-policy-service
bot
added
the
Community
|
Test instance at https://netsourceindex-validation.azurewebsites.net/ |
jjonescz
approved these changes
Jul 16, 2024
333fred
approved these changes
Jul 16, 2024
This was referenced Jul 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a prerequisite for inclusion on source.dot.net.
Roslyn has its own source-indexer instance on sourceroslyn.io, based on an obsolete code snapshot. This PR opts Roslyn in for the main source.dot.net instance, which is regenerated daily from the most recent CI build of all contributing repositories.
Putting asset publication inside individual repositories allows the repo owners who know their code best to fine-tune their build flags and environment.
Please note that there is an issue under active investigation where V2 repository publishing can occasionally fail due to obscure permissions errors from Azure since we switched uploads from SAS to Managed Identity (currently about 6 failures per day total across all repositories)