-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Add support for rich code navigation in GitHub #12855
Changes from all commits
29bcb1a
8ca2ae6
d141ecc
ce3619e
4b69991
d23e51d
fe8e173
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,6 +11,7 @@ jobs: | |
BuildConfiguration: ${{ parameters.configuration }} | ||
BuildPlatform: ${{ parameters.platform }} | ||
WindowsTerminalBranding: ${{ parameters.branding }} | ||
EnableRichCodeNavigation: true | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't see anything using this variable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. apparently it's magic to turn it on in the code nav tooling itself. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, we use this parameter to tell us to run a specific package called RichCodeNav.EnvVarDump, which is needed for some builds so we can get information about the environment the build is running in. |
||
pool: | ||
${{ if eq(variables['System.CollectionUri'], 'https://dev.azure.com/ms/') }}: | ||
name: WinDevPoolOSS-L | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
parameters: | ||
artifactName: 'drop' | ||
|
||
jobs: | ||
- job: CodeNavIndexer | ||
displayName: Run Github CodeNav Indexer | ||
pool: { vmImage: windows-2019 } | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does it have to run on Windows? Windows is much slower than Linux at starting up here. I mean it's fine, but just curious. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Unfortunately right now we do have to run on Windows, but we're working on Linux support! We'll send out a mail once we have that ready so you can switch over! |
||
|
||
steps: | ||
- checkout: self | ||
fetchDepth: 1 | ||
submodules: false | ||
clean: true | ||
|
||
- task: DownloadBuildArtifacts@0 | ||
inputs: | ||
artifactName: ${{ parameters.artifactName }} | ||
|
||
- task: RichCodeNavIndexer@0 | ||
inputs: | ||
languages: 'cpp,csharp' | ||
continueOnError: true |
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.
Oof. Doesn't this mean it's going to run on every push and every rolling build? Won't that end up taking a massive amount of storage space for all those indexes to be saved? I would think we would run it only on
main
or something.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.
That is a good question. Lemme bring in the codenav folks to see what they think
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.
Hi! Holly from the codenav team here! We're fine with this running with such high frequency and the storage load, we actually want to test how well we scale to highly active repos. I will say, most folks who onboard do only run our task on builds of main and a few teams have made a separate .yml file just for the build+codenav tasks so that they can have more fine-tuned control of when it runs, but it's up to you what builds you would find benefit from having navigation on.
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.
My bigger concern is that this will build against 3p code on pull requests. We might want to restrict it like we did the ARM64 build 😄