Since the first job is committing changes to a subversion repository, I think you could have the second job poll that subversion repository (no plugins required). When the first job submits the change to subversion, the second job will see that as a change and will run.
Because the second job is separate from the first job, it will also be possible to run the second job without requiring the first job has run. In that case, the second job will use the most recent binaries placed in the subversion repository by the first job. Neither of those will require any command line calls. They won't require that you examine log files. They let the subversion log polling do the work for you. There is a command line for Jenkins. It is usable on Windows. Refer to https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI Mark Waite >________________________________ > From: louwho <louels...@comcast.net> >To: jenkinsci-users@googlegroups.com >Sent: Thursday, June 28, 2012 7:27 AM >Subject: Re: Windows Jenkins Service, how to determine if 2nd job should be >started? > > >Can anyone else please help me with this. I do not know which plugin to us >(and is there an example of doing this in windows?). Can I use the Jenkins >command line in a windows batch file (Do I have to install Java first, then >what)? Thanks. > >On Tuesday, June 26, 2012 10:07:18 AM UTC-4, louwho wrote: >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? > >
