QESTNET.Upgrade Internal:Creating Build 1.0 - Revision history

Stephen.riddell at 06:38, 4 July 2017

2017-07-04T06:38:36Z

←Older revision		Revision as of 06:38, 4 July 2017
Line 1:		Line 1:
	==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==		==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==

	'''''This content is now somewhat outdated. The scripts for qestnet.upgrade and the executable have been separated. The manifest file in the qestnet database should be manually updated with the required database version (increment for each release). The application files can be reused from any previous release, or rebuilt from the qestnet.upgrade repository until the new scriptrunner is publicly released. The database upgrade scripts and manifest can be produced in one convenient (if confusingly named) zip file from the Legacy Qestnet Database Script Packages project'''''		'''''This content is now somewhat outdated. The scripts for qestnet.upgrade and the executable have been separated. The manifest file in the qestnet database should be manually updated with the required database version (increment for each release). The application files can be reused from any previous release, or rebuilt from the qestnet.upgrade repository until the new scriptrunner is publicly released. The database upgrade scripts and manifest can be produced in one convenient (if confusingly named) zip file from the Legacy Qestnet Database Script Packages project. The specific instructions should be updated by someone who goes through the whole process.'''''

	<ol>		<ol>

Stephen.riddell at 06:37, 4 July 2017

2017-07-04T06:37:52Z

←Older revision		Revision as of 06:37, 4 July 2017
Line 1:		Line 1:
	==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==		==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==

			'''''This content is now somewhat outdated. The scripts for qestnet.upgrade and the executable have been separated. The manifest file in the qestnet database should be manually updated with the required database version (increment for each release). The application files can be reused from any previous release, or rebuilt from the qestnet.upgrade repository until the new scriptrunner is publicly released. The database upgrade scripts and manifest can be produced in one convenient (if confusingly named) zip file from the Legacy Qestnet Database Script Packages project'''''

	<ol>		<ol>
	<li>Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.</li>		<li>Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.</li>

David.lucas at 00:54, 29 January 2016

2016-01-29T00:54:30Z

←Older revision		Revision as of 00:54, 29 January 2016
Line 1:		Line 1:
	==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==		==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==
	<ol>		<ol>
	<li>Checkout the approriate branch for the build from qestnet.~~ugprade~~ repository. E.g. fugro-dbb.</li>		<li>Checkout the approriate branch for the build from qestnet.upgrade repository. E.g. fugro-dbb.</li>
			<li>Ensure the branch is at the current origin head and all required commits for the build are present.</li>
	<li>Update the build parameter in '''package_development.bat''' and '''package_release.bat''' in the root directory with the new build version number. E.g.,		<li>Update the build parameter in '''package_development.bat''' and '''package_release.bat''' in the root directory with the new build version number. E.g.,
	<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''		<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''

David.lucas at 00:51, 29 January 2016

2016-01-29T00:51:23Z

←Older revision		Revision as of 00:51, 29 January 2016
Line 1:		Line 1:
	==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==		==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==
	#Checkout the approriate branch for the build from qestnet.ugprade repository. E.g. fugro-dbb.		<ol>
	#Update the build parameter in package_development.bat and package_release.bat in the root directory with the new build version number. E.g.,		<li>Checkout the approriate branch for the build from qestnet.ugprade repository. E.g. fugro-dbb.</li>
	#: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''		<li>Update the build parameter in '''package_development.bat''' and '''package_release.bat''' in the root directory with the new build version number. E.g.,
	#Run package_release.bat.		<blockquote>C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe build.proj /t:SetVersion;RebuildAll /p:Configuration=Development;MajorVersion=1;MinorVersion=0;Build='''205'''
	#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.		</blockquote></li>
	#Copy the Scripts ~~folder~~ in the root directory to this temporary folder.		<li>Run '''package_release.bat'''.</li>
	#Update the QESTNET.Upgrade.UI.exe.Config file to the below xml.		<li>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.</li>
	<pre>		<li>Copy the folder (and contents) '''Scripts''' in the root directory to this temporary folder.</li>
			<li>Update the '''QESTNET.Upgrade.UI.exe.Config''' file to the below xml.

			<blockquote><pre>
	<?xml version="1.0" encoding="utf-8" ?>		<?xml version="1.0" encoding="utf-8" ?>
	<configuration>		<configuration>
Line 20:		Line 23:
	</connectionStrings>		</connectionStrings>
	</configuration>		</configuration>
	</pre>		</pre></blockquote>
	#Zip the contents of the temporary folder and name the zip QESTNET.Upgrade v1.0.XXX.zip where XXX is the build version number.		</li>
	#Copy the zip file to \\adls0003\Development\Product Distribution\QESTNET.Upgrade\. This will make the release publicly available.		<li>Zip the contents of the temporary folder and name the zip '''QESTNET.Upgrade v1.0.XXX.zip''' where XXX is the build version number.</li>
	#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.		<li>Copy the zip file to '''\\adls0003\Development\Product Distribution\QESTNET.Upgrade\'''. This will make the release publicly available.</li>
	#Tag the commit with 'v1.0.XXX' where XXX is the build version number.		<li>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.</li>
	#Push the commit to github.		<li>Tag the commit with 'v1.0.XXX' where XXX is the build version number.</li>
	#Push the tag to github (tags need to be pushed explicitly).		<li>Push the commit to github.</li>
	#Inform appropriate parties of the new release build.		<li>Push the tag to github (tags need to be pushed explicitly).</li>
	#Have a non-alcoholic beverage as this was too easy.		<li>Inform appropriate parties of the new release build.</li>
			<li>Have a non-alcoholic beverage as this was too easy.</li>
			</li>
			</ol>

David.lucas at 00:43, 29 January 2016

2016-01-29T00:43:00Z

New page

==QESTNET.Upgrade 1.0 Release Build Process (Fugro 4.0)==
#Checkout the approriate branch for the build from qestnet.ugprade repository. E.g. fugro-dbb.
#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'''
#Run package_release.bat.
#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.
#Copy the Scripts folder in the root directory to this temporary folder.
#Update the QESTNET.Upgrade.UI.exe.Config file to the below xml.
<pre>
<?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>

</connectionStrings>
</configuration>
</pre>
#Zip the contents of the temporary folder and name the zip QESTNET.Upgrade v1.0.XXX.zip where XXX is the build version number.
#Copy the zip file to \\adls0003\Development\Product Distribution\QESTNET.Upgrade\. This will make the release publicly available.
#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.
#Tag the commit with 'v1.0.XXX' where XXX is the build version number.
#Push the commit to github.
#Push the tag to github (tags need to be pushed explicitly).
#Inform appropriate parties of the new release build.
#Have a non-alcoholic beverage as this was too easy.