GitHub - dqhoang/hotfix: hotfix tool

Branches Tags

Name		Name	Last commit message	Last commit date
Latest commit History 25 Commits
test		test
.gitignore		.gitignore
README		README
check.py		check.py
compile.py		compile.py
render.py		render.py
research.py		research.py
stage.py		stage.py

Repository files navigation

=Hotfix Helper=

This sequence of utilities takes in a hotfix specifications document of the form:

	<hotfix>
		<title>RPE 3.5.2 Hotfix 7</title>
		<build>RPE-3.5.2.25-HF7-148</build>
		<web>10.1.0.180</web>
		<app>10.1.0.178</app>
		<appspecial>Deploy CaseBusiness.jar as a deployment overlay in WildFly by running Deploy_RPE_352_HF7_38911.bat. Remove previous version first by running Deploy_RPE_352_HF6_38888.bat --remove.</appspecial>
		<offline>10.1.0.179</offline>
		<offlinespecial>Deploy CaseBusiness.jar as a deployment overlay in WildFly by running Deploy_RPE_352_HF7_38911.bat. Remove previous version first by running Deploy_RPE_352_HF6_38888.bat --remove.</offlinespecial>
		<issue>
			<number>38293</number>
			<summary>Optimized Process Overpayment offline. Child issue 38954 tracks an index script for this issue.</summary>
			<file>20151007_1341_38954_SS.sql</file>
			<file>getStagingData.sql</file>
		</issue>
	</hotfix>

and "compiles" it to an instructions document of the form:

	<instructions>
		<build>RPE-3.5.2.25-HF7-148</build>
		<title>RPE 3.5.2 Hotfix 7</title>
		<issue>
			<number>38293</number>
			<summary>Optimized Process Overpayment offline.</summary>
			<file>20151007_1341_38954_SS.sql</file>
			<file>getStagingData.sql</file>
		</issue>
		<database>
			<script>20150910_0124_39022_SS.sql</script>
			<script>20151006_0513_38983_SS.sql</script>
		</database>
		<businessrules>true</businessrules>
		<app>
			<replacement>
				<filename>ITPCoreBusiness.dll</filename>
				<path>C:\RSI\Web Services\ExternalWebService\bin\ITPCoreBusiness.dll</path>
				<path>C:\RSI\Web Services\NetWebServices\bin\ITPCoreBusiness.dll</path>
				<path>C:\RSI\Web Services\Rules Services\bin\ITPCoreBusiness.dll</path>
			</replacement>
			<restartiis>true</restartiis>
		</app>
	</instructions>

and then "renders" this to an HTML document that's ready to go out to sites.

The initial spec XML can be easily made with the Hotfixhelper frontend web app.


==Installation==

Following python packages required:
pip install pystache
pip install markdown


==Development==
Comments on shell script framework: Could modify so that .hotfix doesn't have to be copied every hotfix cycle. This means ironing out the scripts' reliance on what directory you're currently working in, which probably means manually changing a path in a shell script each hotfix cycle.

To do:
* Factor out reliance on /d/hotfix being the path to scripts
* Add --only-missing option to stage.py
* Sort replacements alphabetically within each 'app', 'web', 'offline' section
* Enumerate .xlsx files by name instead of saying 'all .xlsx files'.
* Frontend: When typing issue number, 'enter' creates new issue and puts focus on issue number field.
* Frontend: Create field that quickly populates issue number based on Sai's initial request email. Paste in the email text and it shall create one issue per issue.


Author: mhenry