On Thu, Aug 21, 2014 at 1:43 PM, Wood Peter <peterwood...@gmail.com> wrote:
> Thank you for the replies. > > I'm still testing the setup so I try to keep it as clean as possible. > There is only master branch and everything else is pretty clean minimal > setup done by following the documentation. > > For "Additional Behaviours" all I have is "Strategy for choosing what to > build: Gerrit Trigger". I'm not sure what that does. > Are you using Gerrit to track your source code changes? If so, then you'll probably need help from someone who knows the details of the Gerrit trigger. I don't use Gerrit yet. > If I'm to test a job without the Gerrit Trigger do I need to add > "Additional Behaviours"? > > No, a test job without the Gerrit trigger just needs the URL of the git repository. No additional behaviors are needed. > About the "pull log", actually I wanted to say "Pulling Log". When I go to > any build page, on the left hand side along with "Changes", "Console > Output" and so on, I see another link called "Pulling Log". When I click on > it on the top of the page it says: "This page captures the polling log that > triggered this build". > It's like this one > http://ci.gerritforge.com/job/Gerrit-master/445/pollingLog/ but for me > the page is empty. > That's the "polling log". Jenkins SCM plugins (including the git plugin, mercurial plugin, perforce plugin, and others) can query the source control system periodically to check for changes. If changes are detected, then the job is started. The polling log will report changes are detected after a change is made to the polled repository, and after the polling has run. > Here is my console output: > > Triggered by Gerrit: http://repos.local:8080/20 <http://sdrepos.local:8080/20> > Building in workspace /var/lib/jenkins/jobs/cfproject/workspace > > git rev-parse --is-inside-work-tree # timeout=10 > Fetching changes from the remote Git repository > > git config remote.cfproject.url > ssh://jenk...@repos.mycompany.com:29418/cfengine/cfproject # timeout=10 > Fetching upstream changes from > ssh://jenk...@repos.mycompany.com:29418/cfengine/cfproject > > git --version # timeout=10 > using GIT_SSH to set credentials > > git fetch --tags --progress > ssh://jenk...@repos.mycompany.com:29418/cfengine/cfproject > refs/changes/*:refs/changes/* > > git rev-parse b814adf6b424c10ea8063d29767c85de74971a06^{commit} # > timeout=10 > Checking out Revision b814adf6b424c10ea8063d29767c85de74971a06 > (refs/changes/20/20/1) > > git config core.sparsecheckout # timeout=10 > > git checkout -f b814adf6b424c10ea8063d29767c85de74971a06 > > git rev-parse FETCH_HEAD^{commit} # timeout=10 > > git rev-list 1388d41de4bff273baf6a9282970c013069b2654 # timeout=10 > [workspace] $ /bin/sh -xe /tmp/hudson1833744645105158914.sh > + /usr/local/bin/ci-buildplay.sh > We are good. > + /usr/local/sbin/ci-cfesyntax.sh > Finished: SUCCESS > > Thank you, > > -- Peter > > On Wed, Aug 20, 2014 at 6:43 PM, Mark Waite <mark.earl.wa...@gmail.com> > wrote: > >> >> >> On Wed, Aug 20, 2014 at 7:13 PM, Wood Peter <peterwood...@gmail.com> >> wrote: >> >>> Jenkins-1.567; Git-Plugin-2.2.5; Gerrit-Trigger-2.11.1 >>> >>> I setup Jenkins-Git-Gerrit and everything works as expected. >>> >>> The issue I'm having is that every build shows list of changes starting >>> from the initial commit all the way to the last commit that actually >>> triggered the build. Seems like it doesn't update the local repository and >>> it start from scratch every time a build is triggered. >>> >>> >> Did you inadvertently add the "Additional Behaviour" to "Calculate >> changelog against a specific branch"? That might cause the list of changes >> to appear for each build, even if no changes arrived. >> >> >> >>> My Workspace files are up to date but my Pull Log for the builds is >>> empty. >>> >>> >> I don't recognize the term "pull log". Is that somehow related to the >> Gerrit trigger? >> >> >>> Also if I manually run a build (i.e. not triggered by an event) it does >>> a pull of the very first commit only and then continues with the tests. >>> >> >> I assume that is also something provided by the Gerrit trigger, so I >> don't recognize the concept of pulling a commit into the git plugin. >> >> Can you duplicate the problem without the Gerrit trigger? >> >> Mark Waite >> >> >>> I know I missed some settings somewhere. >>> >>> Any help is appreciated. >>> >>> Thanks, >>> >>> -- Peter >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Jenkins Users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to jenkinsci-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Thanks! >> Mark Waite >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to jenkinsci-users+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
