View source for QESTNET Internal:Creating Build 4.0

==QESTNET 4.0 Release Build Process (Fugro)==
<ol>
<li>Checkout the release-4.0 branch from qestnet repository.</li>
<li>Ensure the branch is at the current origin head and all required commits for the build are present. This may mean a hotfix commit or a merge (--no-ff) branch dev4.0 into release-4.0.</li>
<li>Open the QESTNET.sln and QESTField.sln. Ensure the QESTNET.Custom.Fugro.DataBackbone and QESTNET.Integration.Portal projects are loaded.</li>
<li>Update the AssemblyVersion and AssemblyFileVersion of all AssemblyInfo.cs files with the new version number in both solutions.</li>
<li>Build debug & release QESTNET:</li>
<ol>
<li>Switch to debug.</li>
<li>Re-build the Schema Generator if required.</li>
<li>Upgrade the database you intend to build against, using the qestnet.upgrade tool built for this release. Run any required post-install scripts.</li>
<li>Build the qestlab.data project. See [http://online.spectraqest.com/index.php?title=qestnet_internal:developer_setup_qestnet#build_qestlab.data build qestlab.data].</li>
<li>Re-build QESTNET.sln.</li>
<li>Switch to release.</li>
<li>Re-build QESTNET.sln.</li>
</ol>
<li>Run '''~\QESTNET\copy_all_to_libraries.bat'''.</li>
<li>Create a new folder '''v4.0.XX''' in '''~\Libraries\QESTNET\''' where XX is the build version number. Copy the Debug and Release folders also in this folder, into the new '''v4.0.XX''' folder.</li>
<li>Update the build parameter in '''build-debug-x64.bat''' and '''build-release-x64.bat''' in '''~\QESTNET\QESTNET.Deployment\''' with the new build version number. E.g., 
<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe /t:Rebuild .\QESTNET.Deployment\QESTNET.Deployment.wixproj /p:Configuration=Release;QestnetVersion='''4.0.18'''
</blockquote></li>
<li>Run '''build-release-x64.bat'''.</li>
<li>Run '''package_release.bat'''. This will copy the installer to '''\\adls0003\Development\Product Distribution\QESTNET\'''. Move it to folder '''Fugro'''. This will make the release publicly available.</li>
<li>Switch the '''QESTField.sln''' to release. Publish the solution to a temporary folder.</li>
<li>Zip the contents of the temporary folder and name the zip '''QESTField v4.0.XX.zip''' where XX is the build version number.</li>
<li>Copy the zip file to '''\\adls0003\Development\Product Distribution\QEST Field\'''. This will make the release publicly available.</li>
<li>Commit the qestnet branch changes to git with commit message '''Prepare release v4.0.XX''' where XX is the build version number.</li>
<li>Tag the commit with '''v4.0.XX''' where XX is the build version number.</li>
<li>Push the commit to github.</li>
<li>Push the tag to github (tags need to be pushed explicitly).</li>
<li>Inform appropriate parties of the new release build.</li>
<li>Have a cider as this should be automated.</li>
</li>
</ol>