You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should look into changing this setting, so that we build on all PRs. This helps us verify changes in build.ps1 more easily.
The easiest way to fix this from what I can tell would be to tweak this part to set the NuGet package version like this, unless $env:APPVEYOR_REPO_TAG -eq "True"
(In other words, we will get junk version numbers like 62.0.0-CI34 until we tag the repo; for these builds, we will set the NuGet package version to match the tag just like we've done historically.)
Anyone wants to fix this - feel free, it's up for grabs.
The text was updated successfully, but these errors were encountered:
Remove need for hack checks to determine if the target is a x86 or x64 build
build.ps1 - Remove unused Nupkg variable
Variable was empty and has been removed from nuspec file
Switch to appveyor nuget feed
I'm only pushing packages to the feed when a tag is detected, so this should bring this one step closer. The build script can probably be changed to build a specific version if a tag is detected, with the default being to grab the most recent version available from Spotify. Thoughts?
We should look into changing this setting, so that we build on all PRs. This helps us verify changes in
build.ps1
more easily.The easiest way to fix this from what I can tell would be to tweak this part to set the NuGet package version like this, unless
$env:APPVEYOR_REPO_TAG -eq "True"
(In other words, we will get junk version numbers like 62.0.0-CI34 until we tag the repo; for these builds, we will set the NuGet package version to match the tag just like we've done historically.)
Anyone wants to fix this - feel free, it's up for grabs.
The text was updated successfully, but these errors were encountered: