This section describes the rational for gmStudio's approach to deployment .
...
Table of Contents |
---|
Why Bundle?
One of the unique features of gmStudio is that is allows you to separate code generation from code deployment. This best practice resulted from our work in helping teams perform migrations of very large systems. It works like this: rather than publishing the translated code as separate files and folders immediately as they are produced, gmStudio creates a consolidated text archive that contain all the files. This text archive, or bundle file as we call it, must be explicitly processed, or "deployed", to create the separate files and folders. By default, this feature works behind the scenes and it is extremely fast so you barely notice it. This approach provides additional control and visibility to the migration effort, and having all the generated code in a single file facilitates several useful operations:
- Report an inventory of all code generated for a translation
- Search, or search and replace, all code generated for a translation
- Create a snapshot all code generated for a translation translation
- Compare two snapshots of all code generated for a translation
translation - Compare all generated code for two different translations translations
- Inspect code before deploying it
...
rmdir \gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh
mkdir \gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh
mkdir \gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh\bin\
cat >\gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh\ScanToolUI.csproj <<
'!)(!'
'' ... SrcText Text OF \gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh\ScanToolUI.csproj ...
'!)(!'
cat >\gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh\AssemblyInfo.cs <<
'!)(!'
'' ... SrcText Text OF \gmProj\DemoScanTool\deploy\ScanToolUI_iop_csh\AssemblyInfo.cs ...
'!)(!'
''... REMAINING FILES AND DEPLOYMENT COMMANDS ...
...
cat >
'PATH OF FILE TO CREATE <<'!)(!'
'' ... SrcText Text OF FILE TO CREATE ...
'!)(!'
The translator always writes your translation to a bundle file that you specify in the Translation Script and a separate step, running the deployment tool -- is used to run the bundle file. By default, gmStudio handles all of this behind the scenes.
Viewing Viewing and Reporting your Bundles
...