What I’ve been up to – A: Automation

July 7, 2012 2 comments

Have a look at what’s been said about one of my projects:

Using the deployment automation tool, I just did a hot deploy of the [censored] training system for the first time, literally 5 minutes before a meeting at which I was going to demonstrate it, and the process was almost too intuitive and painless. Very impressive! –John Beaver (Software Developer)

Outstanding work  … Great feedback, especially for a 1.0 release!  The efficiencies you have built into the process and the tool provide material improvements and time savings for the [censored] program!  Looking forward to v2.0 and integration with more applications. Super work! With my utmost gratitude, –Helen Baker (CCT Director)

This rocks—many thanks! I love automation. J Regards, –Tony Niderost (Sr. Director/GM)

GREAT WORK J!!! Thanks, –David Kuhl (VP, Corporate IT)

So what are they talking about you may ask?

I called it our Self Deploy app, and it did just that.

I’m a huge proponent of automation and simplification of complex processes– Even to the extent that I automate myself out of a job 🙂  I’m also a huge fan of Steve Jobs work. Let’s look at few quotes that really speak to me, of  which I read in his biography:

Simplicity is the ultimate sophistication. –Steve Jobs
Simplicity isn’t just a visual style. It’s not just minimalism or the absence of clutter. It involves digging through the depth of the complexity. To be truly simple, you have to go really deep. –Steve Jobs
Steve made devices simpler by eliminating butons, software simpler by eliminating features, and interfaces simpler by eliminating options.

During one point I was on-call 4 weeks in a row; accountable 24/7 to ensure builds were released at the beck and call of anyone in Dev or QA departments.  My motivation was to simplify this disjointed release process that spanned ~30 Linux/Windows servers & took up to an hr, so that anyone could run the deploy, and thereby freeing me  to enjoy MY weekends. 🙂

Every deployment option was given a radio buton, tab, or drop down and a default value so that anyone could run the deploy process.  The goal was a ‘single click’ deploy app and I did everything to reach that goal,.. even to the extent of securely encrypting the user’s credentials to a Windows store so it only needed to be typed on first run.

The UI tab drives deployment to the Windows IIS servers.  My C# app called a batch file, that called Sysinternals PSexec which copied over a powershell script to each remote server and executed it.

The Service tab drives the deployment to the Linux servers.  My C# app called Putty’s Plink utility to execute bash commands remotely on each CentOS server.  The bash script stopped a tomcat instance, copied over a new .War file and configuration files for the given environment.

When the deployment has completed, a summary report pops up with a ‘copy’ button that whomever is running the deployment can copy and paste into a release email to notify the QA department that the build is ready for testing.

UPDATE: I contacted my old colleague and was told they are using the app to this day.  That’s how I judge success!


Replace Icons in Program (notepad++)

December 15, 2011 2 comments

I consider myself a ‘power user’ which really just means I have a ton of windows open in my taskbar throughout the day…  Which makes it really hard to find the app you’re looking for if the icon that happens to be camoflauged by the Windows theme you’re running.

It seems like I’m always fishing for my most used app, Notepadd++, that I use for coding because the green/white icon seems to always be hiding.  I Googled for a way to replace the icon and with a little hunting I came up on this thread, which not only provided a replacement icon, but also a hint as to the program I could use to make this happen:

Resource Hacker!

  • I had to copy the notepad++.exe to my desktop before it would allow me to save (one of those Win7 things)
  • I think I used the 101 resource to replace the icon (comment if I forgot)

Finished product:

Perforce auto login using md5 hash (p4v and cli)

December 14, 2011 4 comments

A coworker of mine showed me a cool way of avoiding having to type your password each time you log into Perforce: An md5 of your password stored in an environment variable, or an .ini file if your using the command line.

1. in p4v, click Connection > Edit Current Workspace. Make a note of your ‘Root’. Mine is C:\depot\

2. Navigate to your ‘Root’ and create an file P4.ini

Mine looks like this:

# This is to tell the sd client what server and port to use
P4PASSWD=(Get this from step 3)

2a: If you’re doing this for p4v, just create these as environment variables instead.

3. Go to one of the following websites and generate the md5 hash of your password and place it in your .ini file for the P4PASSWD value.

  • Note: The md5 hash MUST BE ALL CAPITALIZED. It took a bit of Perforce documentation reading to realize what my problem was.
  • Note, instead of an .ini file, you can create an environment variable called P4PASSWD. I chose to use an .ini because at my work we connect to four different depots using different accounts. Because you can only have one environment variable, the .ini allows you to connect to as many depots as you want as long as the .ini file is placed in the root of your workspace.  Here‘s a good description of the various ways to set these variables and their search order.

4. Add a System Environment variable named P4CONFIG with a value of p4.ini .  This is how Perforce knows to look for our p4.ini file.


You can verify that perforce is finding your p4.ini file by typing from the command line: p4 set. You should see the output of this command matches the contents of your p4.ini file.


Each time you open Perforce, you will not be prompted for your password! Sweet!

Parsing Tomcat Catalina values with Grep/AWK

November 17, 2011 1 comment

Blog Update

I’ve started a new job at a large travel company based in the Pacific North West.  My job functions have shifted from software deployment on Windows, to release engineering in Linux for tomcat web servers.  It’s a completely different world, but I want to continue blogging, so the theme of this blog will be changing to general release engineer topics in Linux.

Parsing Tomcat configuration settings:

In my new position I’ve inherited some bash scripts of which need a major face lift.  One problem I noticed was that between their servers, the deployment directories differ and they were hard coding these values in the script.
Instead of hard coding the values I thought it would be a good idea to simply parse the tomcat configuration files for these values.  This allows the script to be more flexible and run on all their servers.
First I’m parsing the single instance tomcat startup script:
This file contains the CATALINA_BASE location which allows me to build the path to server.xml catalina.properties.
Here’s the grep and awk statement I’m using to find CATALINA_BASE:
CATALINA_BASE=`grep 'CATALINA_BASE=' $Tomcat | awk -F"=" '{print $2}'`
Now that I have the config file locations, I parse each of them for the the Tomcat’s appBase folder (where the .war file gets deployed to)
appBase=`grep 'appBase=' $serverXMLFile | awk -F"=" '{print $3}' | tr -d '"'`                               # ex: /app/webapps
Now that these paths are dynamically built in a script, I can re-use this script in each environment regardless of what customized directory structure they are using for Tomcat.
I love the elegance here.  Think about doing this in any other language and most of the time you’d have to open a file handle and parse the file… this is one line of text. Bash with Sed/Awk is some Very powerful stuff!

C# DTF using locale .NET culture folder and .resources files for translations with MakeSFxCA.exe

August 30, 2011 Leave a comment

Wow, that title is a mouthful.

One of the REALLY cool features of WiX DTF is that it uses MakeSFxCA.exe to create a self-extracting Dll that auto-magically bundles all your project dependencies into one DLL.  When called from your installer at run-time, the files are extracted to your %temp%\MSI*.tmp\ folder and your DLL is called.

But, we had a little bit of trouble getting the out-of-the-box setup to work with .NET localization.

To provide a little background: We’re using an Installshield 2011 Basic MSI project with the Wix Toolkit’s C# Deployment Tools Foundation (DTF) to fire a custom action in the UI Sequence.  The custom action dll displays a Winform of which we need to have localized for strings translations.

However, the out-of-the-box Visual Studio custom action project templates available to you after installing WiX do not properly deploy nested folder structures, which are a necessity for .NET localization.

To visualize, here’s the output of my project as compiled in Visual Studio… notice the .net culture sub-folder

..And here’s my %temp% folder it’s extracting to at runtime…   notice that it’s not respecting the sub-folder with the .net culture naming syntax, and just bundling it all in the same folder. (LocaleTest.resources.dll).  Without the .net culture sub-folder, the .resource file isn’t found and so it defaults back English at run-time.

After a lot of searching I stumbled upon this thread where a user had a similar question:

Is there a way to get MakeSfxCA include everything in my CA project ouput
directory recursively, maintaining folder structure?  It seems to me this
would be the simplest way of ensuring all necessary dependencies are there
at runtime.

The user dug through the source code of MakeSfxCA (yay for open-source!) and found some comments in the code that pointed him to the correct syntax:

Reading the source for MakeSfxCA I found the GetPackFileMap function and
reading the description:  “By default, all files will be placed in the root
of the cab. But inputs may optionally include an alternate inside-cab file
path before an equals sign.”

So this implied to me that on the MakeSfxCA command line, rather than pass ”
$(TargetDir)EULAs\ja-JP\Eula.rtf” I could pass “EULAs\en-US\Eula.rtf= 

I beleive the log output of MakeSfxCA confirmed this:
Packaging files

So, the syntax is to specify the <Virtual File Path at run-time>=<File On Disk>. (Just like a .cab or .zip file)

The user opened a WiX change request to have this fixed along with an updated wix.ca.targets.  However, Jason Ginchereau commented that it wasn’t such a great idea to make it the default behavior.

Here’s what we’ve done to overcome this limitation.  We’ve added the following .bat file as a post-build step to our project that hard codes the .resource files for inclusion into our resulting xxxCA.dll.  Yes, technically MakeSFxCA.exe is being called twice, but the end result is exactly what we needed.

%wix%SDK\MakeSfxCA.exe “$(TargetDir)$(TargetName).CA$(TargetExt)” “%wix%SDK\x86\SfxCA.dll” “$(TargetPath)” “$(TargetDir)Microsoft.Deployment.WindowsInstaller.dll” “$(TargetDir)Seagull.InstallWizard.dll”


REM Languages need to be added once they are available using the following syntax:


After adding the batch file as a post-build step, our translations display property at run-time in our custom UI.


ISICE Validation: Documenting Custom Actions with ISCustomActionReference table

August 5, 2011 Leave a comment

I found a few forum threads relating to Installshield’s ISICE10 validation errors I found interesting.  Basically, you’re supposed to document what each custom action does in the ISCustomActionReference table.
However, it doesn’t appear these ISICE errors will stop you from achieving Windows Logo Testing, so I consider them more of a warning/bestpractice.

MichaelU gives his opinion on the relevance of such ISICE (Installshield Internal Consistency Evaluators) as it pertains to Window’s Logo testing:

 Just for your information, all of the validators named ISICE~~ are custom, and while they are designed to assist with passing the Vista Logo tests, I don’t believe that Microsoft considers our ISICEs to be authoritative. Or, in short, if you run into a problem with a partiuclar ISICE validator, and your concern is acquiring the Vista Logo, it may be better to discuss it with those who run the Logo program. ISICE10 in particular reflects a particular method to document custom actions rather than the Logo goal of having them all documented.

From user DebbieL, a Technical Writer at Installshield:

The errors about specific custom actions not being documented are validation errors for validator ISICE10. Here’s the information in the documentation about this validator:

The intended behavior of each custom action must be documented for the Windows Vista Quality Program. This is especially helpful if system administrators deploy your product to enterprise environments; they sometimes need to know what the custom actions do.

ISICE10 verifies that each custom action in your installation is documented by validating that each entry in the CustomAction table has a corresponding ISCustomActionReference table entry.

Corrective Action
To resolve this validation error, open the Custom Actions view, select the custom action that is mentioned in the error message, and use the Help File Path setting to specify a path to the document that describes the behavior of the custom action. When you specify a value in the Help File Path setting, InstallShield adds a row for that custom action in the ISCustomActionReference table if one has not already been created.

Note that if the custom action is a merge module that is consumed in your installation project, specify the path in the Custom Actions view of the merge module project and then rebuild the merge module.Here is some additional information from the help topic called “Documenting the Behavior of Custom Actions”:

To document the behavior of a custom action in your project:

1. Create a file that describes the intended behavior of the custom action. It does not matter what type of file that you use. Note that each custom action should have its own document.
2. In the View List, under Behavior and Logic, click Custom Actions.
3. In the Custom Actions explorer, click the action that you are documenting.
4. For the Help File Path setting, click the ellipsis button (…) to browse to the file that describes the behavior of the custom action. The file should be a text-based file such as a .txt, .htm, or .rtf file.

TIP: You can specify whether InstallShield should stream the contents of each of the custom action help files into the .msi file at build time. For more information, see the description of the Include Custom Action Help setting for a product configuration in the Releases view.

In another thread, a user explains that he followed the above directions but was still receiving the error.  Here’s the additional setting he needed:

After struggling  […], I found a cause of this problem.
I did not set the Include Custom Action Help setting to “Yes” for the Product Configuration.

To resolve the ISICE10 error, I did the following operations:

In the View List, under Media, click Releases.
Select the product configuration that has the validation problem.
Check the value of Include Custom Action
Help and set the value to “Yes” if it is “No”.