-
Notifications
You must be signed in to change notification settings - Fork 483
Update test projects #722
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: master
Are you sure you want to change the base?
Update test projects #722
Changes from all commits
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 |
|---|---|---|
|
|
@@ -3,7 +3,8 @@ | |
| <PropertyGroup> | ||
| <LangVersion>14.0</LangVersion> | ||
| <NoWarn>$(NoWarn);CS1591;CS3014;CS3003;CS3001;CS3021</NoWarn> | ||
| <NoWarn>$(NoWarn);CS0612;CS0618</NoWarn> <!-- TODO: Remove this line once `[Obsolete]` members have been dealt with. --> | ||
| <NoWarn>$(NoWarn);CS0612;CS0618</NoWarn> | ||
| <!-- TODO: Remove this line once `[Obsolete]` members have been dealt with. --> | ||
| <RepositoryType>git</RepositoryType> | ||
| <RepositoryUrl>https://github.com/castleproject/Core</RepositoryUrl> | ||
| <BuildVersion>0.0.0</BuildVersion> | ||
|
|
@@ -32,6 +33,14 @@ | |
| <ContentTargetFolders>.</ContentTargetFolders> | ||
| </PropertyGroup> | ||
|
|
||
| <PropertyGroup Condition="'$(CI)' == 'True'"> | ||
| <!--Deterministic Build and Source Link settings --> | ||
| <ContinuousIntegrationBuild>true</ContinuousIntegrationBuild> | ||
| <EmbedUntrackedSources>true</EmbedUntrackedSources> | ||
| <IncludeSymbols>true</IncludeSymbols> | ||
| <SymbolPackageFormat>snupkg</SymbolPackageFormat> | ||
| </PropertyGroup> | ||
|
Comment on lines
+36
to
+42
Member
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'm noticing that on local builds, we still get (legacy?) Perhaps it might be better to put both Or do you have a better recommendation?
Contributor
Author
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. As for me - better solution is to implement it in a right way via some articles: for now this change is
Member
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. We're not quite there yet however. Are you saying that non-CI builds should not emit any NuGet packages at all? In that case we'd still need to change something here. (Note that I wasn't suggesting taking the
Contributor
Author
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. You can build nuget packages locally but probably you don't want to publish to nuget your local package symbols that could contains your local file paths, maybe other sensitive information As I understand best practice here is to use it on CI sorry, maybe I'm not filly understand this topic |
||
|
|
||
| <ItemGroup> | ||
| <Content Include="..\..\CHANGELOG.md" /> | ||
| <Content Include="..\..\LICENSE" Pack="True" PackagePath="" /> | ||
|
|
||
This file was deleted.
This file was deleted.
Uh oh!
There was an error while loading. Please reload this page.