The first job does a msbuild of the binaries and then commits the changes
to SVN (if there were any changes), then there is a Post build step (Build
other projects), that executes the second job that builds the installer.
It does this post build step even if there were no changes and no binaries
build ("trigger only if build suceeds") If I knew how, I would prevent
this post build step from running if there had been no changes (there is no
"trigger only if there were changes"... the build always succeeds.
So, the second job kicks off. It has a build step that "executes a windows
batch command" (the cmd file that does the installer build). There is
a Poll SVN to determine if the first job put anything new into the url that
the second job uses, but even though there were no changes from the first
job (and thus nothing new for this job to pull from svn ("no changes
for...since the previous build"), in the console output, the command file
is executed. There is a post build step that then copies the installer
project to a place that everyone can get to it. There being no change from
the last version of the installer that was created, I do not wish this to
happen. Again, I wish I could prevent this post build step from happening.
When I look at the console output of the second job
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?
