There is a bat file in the project that looks like this:

util\curl\curl.exe https://server:port/route > latest.zip
util\7za.exe e -ogame -y latest.zip
del latest.zip

This uses a CURL command (which can be customized to include authorization etc) to download the zip file which was built by the CI Joe server, and extract the needed EXE/DLL files to the non-coder’s machine. I should probably do a blog post on this part of the process as well.

Do NOT zip assets into big files. That was part of the “bad” example hehe. It does terrible things to the size of the repository, and is really not a correct use of version control.

Im curious about what each build process involves, specially under windows, a bat file? How deep into this processes you use ruby? Would be intersting to hear some experiences on the low level, as how you made the handled the process of building, packaging and uploading to a repo the latest build, in the different plataforms.

For the wip art assets, we just use a different folder in the svn, so the standard update doesnt get cloged with them. Why zip’em into big files?

One thing that has worked out pretty well for the last few projects on the art side strangely enough is Dropbox. It keeps a 30 day history of files and allows us to share and keep art source files in one spot without bloating SVN for everyone else. Love me some Dropbox.