Support automation for Windows

[tomschenkjr]

Right now, a substantial portion of the workflow automation is based on Bash scripts (.sh).

The following files need to be transitioned to be Windows supportable. Namely, the following files need to be transitioned to a Windows-supportable format (i.e., batch scripts):

• Standard_ETL.sh
• The four-by-four scripts (i.e., abcd-1234.sh)

[shua123]

Have you tried using cygwin for running .sh in Windows?

[tomschenkjr]

Looking for a .bat native solution so we don't create dependencies on other applications.

[shua123]

.sh files to convert:

• ETL/Setup-Script.sh
• ETL/Standard_ETL.sh
• DataSync/load_preferences.sh
• The four-by-four scripts (i.e., abcd-1234.sh)

[lm8]

Most MinGW Windows developers use msys and bash. Batch (.bat) doesn't offer the functionality of a bash shell. I'm writing a cross-platform build tool and I'm using bash (even on DOS). There's a native build of bash called winbash ( http://win-bash.sourceforge.net/ ). I've built it from source. Swiss also includes a bash-like shell program ( https://github.com/minoca/swiss ) and is a lot like Busybox. It builds easily on Windows. There's also a port of Busybox to Win32. If you want something that's not dependent on a program you need to build or install, you can look into using JavaScript. An interpreter comes with Windows and it offers more functionality than bat files. There's a series of good articles on using JScript as a batch scripting language ( https://blogs.msdn.microsoft.com/garretts/2009/05/15/using-jscript-as-a-batch-scripting-language-part-ii/ ).