-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Fix nuget package explorer flags #13057
Fix nuget package explorer flags #13057
Conversation
/azp run net - core - ci (Build Test Linux) |
No pipelines are associated with this pull request. |
/azp run net - core - ci |
Azure Pipelines successfully started running 1 pipeline(s). |
eng/Directory.Build.Data.props
Outdated
@@ -35,6 +35,10 @@ | |||
<AddDotnetfeedProjectSource>false</AddDotnetfeedProjectSource> | |||
</PropertyGroup> | |||
|
|||
<PropertyGroup Condition="'$(TF_BUILD)' == '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.
I don't think TF_BUILD is ever set any where. We will need to figure out the better condition.
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.
TF_BUILD property is actually set as a predefined variable for Azure DevOps
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.
OK. Do we know what exactly setting this ContinuousIntegrationBuild option ends up doing? Or why it cannot be set all the time?
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.
The best I can tell from here is that ContinuousIntegrationBuild
property informs the SDK that it is running on the CI server which is by default deterministic. The problem I was having earlier was that it also set DeterministicSourcePaths
to true which caused projects that did not reference the SourceLink package to break because SourceRoot
property was not set. However for all our Shipping Client Libraries this problem is not occurring since they reference the SourceLink package.
Am not sure what else this property affects at this point except that it seems to be a recommended setting.
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.
Do we know if this make us green from the nuget package manager standpoint? I believe that is our primary reason for trying to make this change.
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.
Yes, I tested and it does make us green.
b235d78
to
5fc839e
Compare
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.
This is release week so we might want to hold off on this change until afterwards just to be sure this doesn't impact any of those releases.
Enable
ContinuousIntegrationBuild
for CI builds. This should make packages deterministic as far as Nuget Package Explorer is concerned.TF_BUILD
property is set as a predefined variable for Azure DevOpsBump up template version since preview.15 was released for testing.