The first job does a MSBuild of the binaries, and then commits them into a
SVN repository that the second job will pull from. The second job uses the
stand alone (command line), build of Installshield. This second job can
either be manually started by someone using the dashboard, or, when the
first job determines that there were changes that need to be included in a
new build of the installer. The question is, how can the first job
determine that there were changes, and that the second job needs to be
kicked off? Checking the log files, I can see that there are differences
in some of the log files in the Builds folder, (one file in particular is
the changelog.xml file). In a cmd file, I could examine these files,
determine if there were changes, and then kick off a build (or not), or, is
there something in jenkins that I could use to determine if the second job
should be executed? If I used the cmd to examine the log files, how do I
then kick off the second job...is there a windows command line for Jenkins?
