Build is now being triggered by detection of changes in the repositiry BUT I can't explain why it is working now and not before as I have no changes. Maybe small gremlins at work that will surface sometime later .. but for now all is good,
Pete On May 13, 5:11 pm, Pete Long <petelon...@gmail.com> wrote: > Hi > > I going through the “Jenkins – The Definitive Guide” to basically > learn about this tool. I am finally able to configure a new maven job > to build the project, > > git://github.com/PeteLong/game-of-life.git > > I have configured the job to monitor the repository for changes every > 5 mins and only to perform the build if there has been a change, > However, the job seems to detect a change - when there is no change - > and performs a another build when it shouldn't have. > > There no changes reported in the "Changes" > > However the "Polling Log" reports a change :- > > Polling Log > View as plain text This page captures the polling log that > triggered this build. > > Started on 13-May-2012 17:06:03 > Using strategy: Default > [poll] Last Build : #12 > [poll] Last Built Revision: Revision > 8bfe65368376438597d51511b4fc854a1cb918b6 (origin/releases) > Fetching changes from the remote Git repositories > Fetching upstream changes from git://github.com/PeteLong/game-of-life.git > Polling for changes in > Seen branch in repository origin/HEAD > Seen branch in repository origin/continuous-delivery-demo > Seen branch in repository origin/feature-history > Seen branch in repository origin/feature-new-look-and-feel > Seen branch in repository origin/game-history-feature > Seen branch in repository origin/integration-branch > Seen branch in repository origin/master > Seen branch in repository origin/releases > Seen branch in repository origin/tdd-labs > Seen branch in repository origin/tdd-training > Done. Took 1.2 sec > Changes found > > Any suggestions as to why this is happening please ? > > Thank you > > Pete
