-
Notifications
You must be signed in to change notification settings - Fork 841
Add fsi to proto build, move version validation to ci only #6387
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
Conversation
|
(@KevinRansom Just to say I've always wanted to avoid FSI in the proto build, since I can imagine a future where FSI is a separate tool in a separate repository. But it's no big deal, and maybe these version checks can be removed altogether anyway) |
| Copy-Item "$ArtifactsDir\bin\fsc\$bootstrapConfiguration\$bootstrapTfm\*" -Destination $dir | ||
|
|
||
| Write-Host "Cleaning Bootstrap compiler artifacts" | ||
| Run-MSBuild $projectPath "/t:Clean" -logFileName "BootstrapClean" -configuration $bootstrapConfiguration |
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.
Why is the clean step getting removed?
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.
Because it just deletes a few files from fsc\Proto\net46, and looks odd.
|
@dsyme, The proto compiler is really an artifact of this repo, we just need one that we can rely on for build tasks. We could either use the LKG or build and execute one in the build. For now it seems as if building one during the proto build phase is a reasonable choice, and gives us better coverage. |
So .. at the end of the build it does some versioning validation, it takes a while and only really needs doing on the ci and official builds. It used the product build version of fsi.exe, which is not always built.