Jump to content

QESTNET Internal:Creating Build 4.0: Difference between revisions

From QESTonline
VisualWikitext
No edit summary
 
No edit summary
 
Line 10: Line 10:
<li>Re-build the Schema Generator if required.</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>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>Build the qestlab.data project. (generate schema, compile, generate views, compile). 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>Re-build QESTNET.sln.</li>
<li>Switch to release.</li>
<li>Switch to release.</li>

Latest revision as of 23:11, 21 March 2016

QESTNET 4.0 Release Build Process (Fugro)

  1. Checkout the release-4.0 branch from qestnet repository.
  2. 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.
  3. Open the QESTNET.sln and QESTField.sln. Ensure the QESTNET.Custom.Fugro.DataBackbone and QESTNET.Integration.Portal projects are loaded.
  4. Update the AssemblyVersion and AssemblyFileVersion of all AssemblyInfo.cs files with the new version number in both solutions.
  5. Build debug & release QESTNET:
    1. Switch to debug.
    2. Re-build the Schema Generator if required.
    3. Upgrade the database you intend to build against, using the qestnet.upgrade tool built for this release. Run any required post-install scripts.
    4. Build the qestlab.data project. (generate schema, compile, generate views, compile). See build qestlab.data.
    5. Re-build QESTNET.sln.
    6. Switch to release.
    7. Re-build QESTNET.sln.
  6. Run ~\QESTNET\copy_all_to_libraries.bat.
  7. 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.
  8. 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.,

    C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe /t:Rebuild .\QESTNET.Deployment\QESTNET.Deployment.wixproj /p:Configuration=Release;QestnetVersion=4.0.18

  9. Run build-release-x64.bat.
  10. 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.
  11. Switch the QESTField.sln to release. Publish the solution to a temporary folder.
  12. Zip the contents of the temporary folder and name the zip QESTField v4.0.XX.zip where XX is the build version number.
  13. Copy the zip file to \\adls0003\Development\Product Distribution\QEST Field\. This will make the release publicly available.
  14. Commit the qestnet branch changes to git with commit message Prepare release v4.0.XX where XX is the build version number.
  15. Tag the commit with v4.0.XX where XX is the build version number.
  16. Push the commit to github.
  17. Push the tag to github (tags need to be pushed explicitly).
  18. Inform appropriate parties of the new release build.
  19. Have a cider as this should be automated.
Retrieved from "http://online.spectraqest.com/index.php?title=QESTNET_Internal:Creating_Build_4.0&oldid=29619"