automated-deploy

Background: writing an automated release script to export changed files between versions from SVN and upload to remote server. The svn log command shows modified files and properties, but seems to not distinguish its verbose output between a content modification over property modifications. Am I reading this output wrong, or is there an easy way to get a list of changed files between revisions whilst ignoring prop changes Here's my sample cmd: #: svn log "someurl" -r 2210:HEAD -v -q Output: ------------------------------------------------------------------------ r2211 | author | 2010-02-08 12

For a number of web-applications I need something like Capistrano to automate deployment. I know Capistrano can be used to deploy non-ruby applications but I'm not familiar with Ruby, so I expect writing deployment configurations can be a bit of a pain. So I was wondering, are there any alternatives to Capistrano written in either Perl of Lua? Also, forgot to mention, the platform running the deployments is Windows (XP). So Capistrano is already more or less out of the question. Although I found out it can run with the MINGW32 Bash shell that comes with Git for Windows. draegtun Not sure there

I am currently working on a Cordova project and had the problem that 8 was appended mysteriously to the versionCode of my project. For example: My original Version code was 100, the new Version code is 1008 I tracked the problem through my whole build pipeline and found the responsible code in the Gradle Build script. if (Boolean.valueOf(cdvBuildMultipleApks)) { productFlavors { armv7 { versionCode cdvVersionCode ?: defaultConfig.versionCode + 2 ndk { abiFilters "armeabi-v7a", "" } } x86 { versionCode cdvVersionCode ?: defaultConfig.versionCode + 4 ndk { abiFilters "x86", "" } } all { ndk {

What is the best way to automatically install an MSI file or installer .exe? We want to do some automated testing from our build system on the installed copy of the product. Our installer has the usual license acceptance screen, install location, etc. As FryHard pointed out there are two options in particular that seem handy: "/quiet" - no use interaction "/passive" - process bar only, unattended mode Franci Penov To automate the installation of an MSI package, you can use the /I option, like this: msiexec.exe /qn /i mypackage.msi Keep in mind that you need to specify the properties the MSI