forked from microsoft/nodejstools
-
Notifications
You must be signed in to change notification settings - Fork 0
Creating a Signed Build
Matt Bierner edited this page Apr 1, 2016
·
4 revisions
[MICROSOFT INTERNAL ONLY] These instructions kick off the build for all versions of Visual Studio installed on the machine and use the -release flag to send them for signing on our signing servers. We currently build for Visual Studio 2012, 2013, and 2015.
- Log into the build machine (ask Sara or Bill for machine name and permissions)
- Our build machines have been configured and approved for use with codesigning.
- If you're using our MicroBuild servers (which do our nightly builds), the bits will be available at:
\\cpvsbuild\drops\nodejstools\NTVS_Out. Otherwise you should specify an-outdirin the next step
- From the PowerShell prompt that is open (or open a new one)
- Sync the changes (
git pull origin master) - Open a PowerShell prompt
- run
.\Setup\BuildRelease.ps1* Pass-dev -releasefor a dev build * Pass-name "x.y" -releasefor an RTM build * Pass-name "x.y zzz" -releasefor "Alpha", "Beta", "Beta #", "RC", "RC #" builds * Or callGet-Help .\Setup\BuildRelease.ps1for more info