Reply To: Automating changes from development to production

[Richard Hart]

We perform almost all of our translation code in TCL.  We also use Unix links as we have many sites that share the same code. When we have a change to implement, we create a second ‘tclprocs’ directory so the link can be changed and the current code is not ‘lost’.

The upgrade script (codeInstall.sh)  uses the file name as parameters to determine the tclprocs link, sites to check and threads within the sites and the RCS revision of the script

eg

cI:ccm1:ccm_prod:ris_:ccm_tables_ris:1.19.sh -> /hci/InfoHEALTH/bin/codeInstall.sh

The script, when executed will process all sites and bounce each thread, checking the log file to ensure that the correct revision has been installed.

Once completed, it reports the resuts.

We have ‘dummy’ prodcution sites that use the same links, so the code installation can be tested on the ‘real’ production setup.

A ‘backout’ version does the same thing,  using the old link.

For NetConfig changes, we generally use links to the NetConfig file, so a quick switch back is easy.