"Emergency" lanes? about housekeeping HOT 5 CLOSED

@micdenny thoughts?

from housekeeping.

the following simple PS script should do the trick:

$root = (split-path -parent $MyInvocation.MyCommand.Definition) + '\..'
$version = [System.Reflection.Assembly]::LoadFile("$root\< assembly path >").GetName().Version
$versionStr = "{0}.{1}.{2}" -f ($version.Major, $version.Minor, $version.Build)

Write-Host "Setting .nuspec version tag to $versionStr"

$content = (Get-Content $root\< Nuget spec file >.nuspec) 
$content = $content -replace '\$version\$',$versionStr

$content | Out-File $root\< compiled output >.compiled.nuspec

& $root\NuGet\NuGet.exe pack $root\< compiled output >.compiled.nuspec

As far as I have understood the assembly version is set by the AppVeyor build, thus the following line will always output 1.0.0:

$version = [System.Reflection.Assembly]::LoadFile("$root\< assembly path >").GetName().Version
$versionStr = "{0}.{1}.{2}" -f ($version.Major, $version.Minor, $version.Build)

That is only downside that can be easily overcome manually setting the version at the command line given that this proposal is to reduce the pain in some corner case scenarios.

from housekeeping.

The PS script could also use the AppVeyor local config file as the source for the version values, given that the process will be used only when working locally we have no interest at all in setting the correct version values in the AssemblyInfo file, the aim is to create the NuGet package.

Given the aim the script is also not interested at all in debug or release build, it will be debug only.

from housekeeping.

each time a PR is built the resulting artifacts, thus the NuGet package as well, are stored by AppVeyor on the build server, the developer could manually download them and host them on a local/offline NuGet server

artifacts for PR are already pushed on AppVeyor and they are free to be downloaded by everyone:

I think this is the easiest way, to avoid adding to much complex on the build process, and leave an easy way to instantly test a PR, just download the nuget package and use it.

And listen this, appveyor has also got its own nuget feed for this use-cases! 😄

for instance Radical project has this appveyor public nuget feed: https://ci.appveyor.com/nuget/radical-beci3al3osa3

and every build package will go there, even the PR that does not create a new build number, but in those cases the last build will overwrite the previous package, but it's just a matter of correctly dump the version on the PR and you're good to go, or of course just manually download the package or binaries.

from housekeeping.

I just tested this and everything worked like a charm. Closing.

from housekeeping.