QESTNET.Upgrade Internal:Creating Build 1.0

QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)

1. Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.
2. Ensure the branch is at the current origin head and all required commits for the build are present.
3. Update the build parameter in package_development.bat and package_release.bat in the root directory with the new build version number. E.g.,

   C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build=205

4. Run package_release.bat.
5. Copy QESTNET.Upgrade.dll, QESTNET.Upgrade.UI.exe and QESTNET.Upgrade.UI.exe.Config in ~\QESTNET.Upgrade\bin\Release\ to a temporary folder for zipping.
6. Copy the folder (and contents) Scripts in the root directory to this temporary folder.
7. Update the QESTNET.Upgrade.UI.exe.Config file to the below xml.

   <?xml version="1.0" encoding="utf-8" ?>
   <configuration>
      <startup useLegacyV2RuntimeActivationPolicy="true"> 
         <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
      </startup>
      <appSettings>
         <add key="manifestPath" value="./Scripts/database_upgrade.qn.manifest" />
      </appSettings>
      <connectionStrings>
         <!--<add name="Example" connectionString="data source=ADLS0007\CUSTOMER2008R2;initial catalog=QESTLab_EXAMPLE;integrated security=True;multipleactiveresultsets=True;Asynchronous Processing=True;App=QestnetUpgrade"/>-->
      </connectionStrings>
   </configuration>
   

8. Zip the contents of the temporary folder and name the zip QESTNET.Upgrade v1.0.XXX.zip where XXX is the build version number.
9. Copy the zip file to \\adls0003\Development\Product Distribution\QESTNET.Upgrade\. This will make the release publicly available.
10. Commit the qestnet.upgrade branch changes to git with commit message 'Prepare release v1.0.XXX' where XXX is the build version number. The AssemblyVersion classes, database_upgrade.qn.manifest and package batch files would have changed.
11. Tag the commit with 'v1.0.XXX' where XXX is the build version number.
12. Push the commit to github.
13. Push the tag to github (tags need to be pushed explicitly).
14. Inform appropriate parties of the new release build.
15. Have a non-alcoholic beverage as this was too easy.