MCS Build and Release Guide - Revision history

Anw: Minor correction

2020-02-07T14:52:41Z

Minor correction

← Older revision		Revision as of 16:52, 7 February 2020
Line 65:		Line 65:
	* Update ''Performance Notes'' section, to indicate where performance of the system or the operation might be impacted by the changes in this release.		* Update ''Performance Notes'' section, to indicate where performance of the system or the operation might be impacted by the changes in this release.
	* Update ''Related Releases'' section, to show related releases, for this system or any other system. For example, if an MCS release is dependent on a specific C-TMS release, reference that here.		* Update ''Related Releases'' section, to show related releases, for this system or any other system. For example, if an MCS release is dependent on a specific C-TMS release, reference that here.
	* Update ''Technical Changes & Special Notes'' section, for any other technical information that the customer might need to know. For example, if the changes require specific hardware or hardware configuration, for example a scanner, a signature pad, a specific monitor size, list this here.		* Update ''Technical Changes & Special Notes'' section, for any other technical information that the customer might need to know. For example, if the changes require specific hardware or hardware configuration, for example a scanner, a signature pad, a specific monitor size, list this here. Any system tasks or changes that must be made to the application that cannot be made by the customer should also be listed here.

	Save the release note in \\spekefs2012\Projects\Releases\MCS\Release Notes\.		Save the release note in \\spekefs2012\Projects\Releases\MCS\Release Notes\.

Anw: Added details of how to create release notes.

2020-02-07T14:51:22Z

Added details of how to create release notes.

@@ Line 40: / Line 40: @@
 Zip the folder to the same name.
 Create a release note in \\spekefs2012\Projects\Releases\MCS\Release Notes\.
 Update the release log in \\spekefs2012\Projects\Releases\MCS\.

Anw: Updated release process.

2020-02-07T09:40:16Z

Updated release process.

← Older revision		Revision as of 11:40, 7 February 2020
Line 32:		Line 32:

	== Prep for Release ==		== Prep for Release ==
	Copy the local release folder and contents to \\spekefs2012\Projects\~~Product~~\MCS~~\Release Logs~~\Release\.		Copy the local release folder and contents to \\spekefs2012\Projects\Releases\MCS\Release\.

	Rename ''Web.config'' to ''Web.config.release''.		Rename ''Web.config'' to ''Web.config.release''.
Line 39:		Line 39:

	Zip the folder to the same name.		Zip the folder to the same name.

			Create a release note in \\spekefs2012\Projects\Releases\MCS\Release Notes\.

			Update the release log in \\spekefs2012\Projects\Releases\MCS\.


Line 55:		Line 59:

	Restart the system through IIS.		Restart the system through IIS.

			Inform the customer through email with the release note attached.


	[[Category:Developer Guides]]		[[Category:Developer Guides]]
	[[Category:Technical]]		[[Category:Technical]]

Anw: Created new MCS Build and Release Guide

2019-12-23T11:02:21Z

Created new MCS Build and Release Guide

New page

{{Note}} This is a developer guide.

== Pre-Requisites ==
See [[Development Notes]] for details of development environment set-up.

Start with the QA TFS stream.

Create a new TFS branch for the new version.

Ensure that all code has been brought in or created in this stream.

Change the JavaScript and Build versions:
* app.js - change MCS.App.Version to the new version number.
* Web.config - change JSVersion to the new version number.

Ensure that the code builds.

Check in all code changes to the new TFS branch.

== Build the Release ==
Right-click on ''WebSite''.

Select ''Publish Web App''.
* Connection:
** File System - specify a local target location.
* Settings:
** Configuration: Release.
Click '''Publish'''.

== Prep for Release ==
Copy the local release folder and contents to \\spekefs2012\Projects\Product\MCS\Release Logs\Release\.

Rename ''Web.config'' to ''Web.config.release''.

Rename this copied folder to the version name e.g. MCS_v.vv.vv.vvv.

Zip the folder to the same name.

== Release ==
On the customer machine, locate the customer MCS installation to be updated.

Delete any prior back-ups if appropriate.

Back-up the existing folder and zip it.

Copy the new release into the MCS installation folder.

Extract the contents of the new release zip over the existing folder.

Check and compare ''Web.config'' to ''Web.config.release'' - make any changes to the customer MCS installation version to reflect new keys added to the file.

Restart the system through IIS.

[[Category:Developer Guides]]
[[Category:Technical]]