Hiya, first of all if you expect help try a more convenient formatting like *line breaks*. Your text is SOO annoying that I had to think twice if I really want to read your case and reply on it ...
There are many approaches to achieve your solution. Using the changelog file from Jenkins is desperate approach but possible. I would probably create a build artifact that contains the necessary information. The advantage is, it is in your workspace and can be archived easily. This routine could as example run in job 1 or 2. The plugin conditional build step could then be configured to process a follow up on changes or not. You could in that case let the plugin look for a file (the created changelog), parameters or strings to decide to skip or run the jobs single build steps Take care Jan Am Dienstag, 26. Juni 2012 16:07:18 UTC+2 schrieb louwho: > > 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?
