Release Process: Difference between revisions

From EPOD
VisualWikitext
No edit summary
No edit summary
Line 1: Line 1:
*Create a folder within the <pre>...Projects\EPOD\_Development\_Releases\Development</pre> at the begining of a development/release cycle.
*Check in any outstanding changes.
*Copy the contents of the releases template folder to the folder you have just created.
*Update to make sure you have the latest programs for all projects.
*Update the version numbers in the AssemblyInfo.cs file(s).
**If releasing the admin client the versions in the four projects (ePOD_AutoExport, ePOD_WebApp, ePOD_WebServices and EPODServer) must be kept the same.
**If releasing the pda client the versions in the two projects (ePODClient and ePODClientUpdater) can be different.
*Copy the release template folder <pre>P:\EPOD\_Development\_Releases\ePOD Release Vx.xx.xxx</pre> to create a release directory.
*Rename the release directory replacing Release with either Admin or PDA (depending on what is being released) and updating the x.xx.xxx to the new version number.
*Any SQL changes should be placed within the SQL\Upgrade folder
*Any SQL changes should be placed within the SQL\Upgrade folder
*Delete any unused subfolders (e.g. the PDA subfolder if releasing the admin).
*Enter any required release notes in the ePOD Release.txt file in the release directory.


==Releasing Web_App==
==Releasing Web_App==
*Using Visual Studio get the latest version of both the Web_App and the ePOD_Server classes.
*Use the publish option against the ePOD_WebApp project (right click project and select publish or select publish ePOD_WebApp option in the Build menu).
*Use the publish option against the Web_App.
**Set the Publish method to File System.
*Select to publish to a file store to enter the file location of the ADMIN folder within this releases folder.
**Set the Target Location to the Admin folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD Admin V1.32.7\Admin).
*Update the folder name to show the version number
*In folder used for the publish delete the web.config file (if present).
*The application will build and publish, the contents of this folder can then be dropped onto any server.
*In folder used for the publish go into the WebServices\Calidus_ePOD\PDAUpdates subdirectory and delete the UpdatesInfo.xml file (if present).
*To release copy the contents of the folder used for the publish to the application folder on the target machine, overwriting any existing files. Do not delete any files (the web.config is not released and the contents of the PDAUpdates folder created by a PDA release).
 


==Releasing PDA==
==Releasing PDA==
*Using Visual Studio get the latest version of the PDA_Client.
*Set the Debug/Rlease drop-down to Release.
*Update the version number in the Properties.cs to the next increment.
*Build the ePODClientInstaller, ePODUpdateInstaller and ePODClientInstallerComplete projects.
*Select the three installer projects, right click and click the build option.
**To build right click the project and select Build.
*Within your working area you will have three cab files, zip these files and label this as Standard (or Client if for a specific client) as a version number.
**The ePODClientInstaller and ePODUpdateInstaller projects must be built before the ePODClientInstallerComplete
*Create the following XML file and put this within the zip folder.
*Copy the three cab files from your local ePOD_AutoExport\bin\Release folder (e.g. C:\Projects\EPOD\ePOD_WebApp\ePOD_AutoExport\bin\Release) to the PDA folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD PDA V1.31.1.9\PDA).
 
*To release:
<pre>
**Copy the three cab files from the release PDA directory to the PDAUpdates directory on the target machine. This direcotry is below the Admin web application directory in the WebServices\Calidus_ePOD subdirectory.
<?xml version="1.0" encoding="utf-8" ?>
**In the same PDAUpdates directory update the version numbers in the UpdatesInfo.xml file.
<UPDATES>
  <EPOD_CLIENT version="XX.XX.XX.XX" url="http://Release URL/EPOD/WebServices/Calidus_ePOD/PDAUpdates/EPODClientInstaller.CAB" required="Y" />
  <EPOD_UPDATER version="XX.XX.XX.XX" url="http://Release URL/EPOD/WebServices/Calidus_ePOD/PDAUpdates/ePODUpdaterInstall.CAB" required="Y" />
</UPDATES>
</pre>


*Copy this to the PDA folder updating the version number on the folder.
*Extract this folder to the following directory
<pre>
  Release Folder\Admin Vxx.xx.xx.xx\webservices\calidus_epod\PDAUpdates\
</pre>


==AutoExport==
==AutoExport==

Revision as of 18:36, 12 December 2012

  • Check in any outstanding changes.
  • Update to make sure you have the latest programs for all projects.
  • Update the version numbers in the AssemblyInfo.cs file(s).
    • If releasing the admin client the versions in the four projects (ePOD_AutoExport, ePOD_WebApp, ePOD_WebServices and EPODServer) must be kept the same.
    • If releasing the pda client the versions in the two projects (ePODClient and ePODClientUpdater) can be different.
  • Copy the release template folder 
    P:\EPOD\_Development\_Releases\ePOD Release Vx.xx.xxx
    to create a release directory.
  • Rename the release directory replacing Release with either Admin or PDA (depending on what is being released) and updating the x.xx.xxx to the new version number.
  • Any SQL changes should be placed within the SQL\Upgrade folder
  • Delete any unused subfolders (e.g. the PDA subfolder if releasing the admin).
  • Enter any required release notes in the ePOD Release.txt file in the release directory.


Releasing Web_App

  • Use the publish option against the ePOD_WebApp project (right click project and select publish or select publish ePOD_WebApp option in the Build menu).
    • Set the Publish method to File System.
    • Set the Target Location to the Admin folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD Admin V1.32.7\Admin).
  • In folder used for the publish delete the web.config file (if present).
  • In folder used for the publish go into the WebServices\Calidus_ePOD\PDAUpdates subdirectory and delete the UpdatesInfo.xml file (if present).
  • To release copy the contents of the folder used for the publish to the application folder on the target machine, overwriting any existing files. Do not delete any files (the web.config is not released and the contents of the PDAUpdates folder created by a PDA release).


Releasing PDA

  • Set the Debug/Rlease drop-down to Release.
  • Build the ePODClientInstaller, ePODUpdateInstaller and ePODClientInstallerComplete projects.
    • To build right click the project and select Build.
    • The ePODClientInstaller and ePODUpdateInstaller projects must be built before the ePODClientInstallerComplete
  • Copy the three cab files from your local ePOD_AutoExport\bin\Release folder (e.g. C:\Projects\EPOD\ePOD_WebApp\ePOD_AutoExport\bin\Release) to the PDA folder within the release directory (e.g. P:\EPOD\_Development\_Releases\ePOD PDA V1.31.1.9\PDA).
  • To release:
    • Copy the three cab files from the release PDA directory to the PDAUpdates directory on the target machine. This direcotry is below the Admin web application directory in the WebServices\Calidus_ePOD subdirectory.
    • In the same PDAUpdates directory update the version numbers in the UpdatesInfo.xml file.


AutoExport

  • Using visual studio get the latest version of the AutoExport
  • Use the publish option.
  • Copy the contents of the build folder typically (Project\Release) to your release folder


  • At this point this should be deployed to Dev and Test.
Retrieved from "https://calidusassist.adcservices.apteancloud.com/calidus-assist/EPOD/index.php?title=Release_Process&oldid=543"