Start some basic documentation on automating app packaging via TeamCity (source Issue #737)

This commit is contained in:
Ken Bailey
2016-09-06 22:28:53 -06:00
parent f46d326503
commit 2061ee4f4e
2 changed files with 23 additions and 0 deletions

22
docs/using/teamcity.md Normal file
View File

@@ -0,0 +1,22 @@
| [docs](..) / [using](.) / teamcity.md
|:---|
# Team City Packaging
## Adding the Packaging Step
When TeamCity pulls down your code, the squirrel.exe will sit under packages if it was added to your solution using NuGet.
1. Add a NuGet Pack process which will create the .nupkg based on a .nuspec file to ensure the package is correct.
2. Create a command line build process and add the following:
~~~
%system.teamcity.build.workingDir%\packages\squirrel.windows.1.4.0\tools\squirrel --releasify [BUILD_SERVER_NUPKG_PATH]\%system.build.number%.nupkg -r [OUTPUT_PATH]
~~~
**Note:** Paths may vary depending on your structure so make sure to update the path information above correctly.
This will cause the appropriate files to be created just as if you had run it from the Package Manager Console.