Every build has all commits listed in the Changes page

[Wood Peter]

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.

My Workspace files are up to date but my Pull Log for the builds is empty.

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 know I missed some settings somewhere.

Any help is appreciated.

Thanks,

-- Peter

[Mark Waite]

On Wed, Aug 20, 2014 at 7:13 PM, Wood Peter <peterw...@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-use...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks!

Mark Waite

[DarrelVun]

I had this happen on my Jenkins instances too nearly a year ago.  I cleared it by upgrading to Git Client plugin 1.4.3 version.  See https://issues.jenkins-ci.org/browse/JENKINS-18995

Git Client plugin has had many versions since then.  But perhaps that's worth investigating.


Regards,
Darrel V.

[Wood Peter]

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.

If I'm to test a job without the Gerrit Trigger do I need to add "Additional Behaviours"?

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.

Here is my console output:

Triggered by Gerrit: http://repos.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://jen...@repos.mycompany.com:29418/cfengine/cfproject # timeout=10
Fetching upstream changes from ssh://jen...@repos.mycompany.com:29418/cfengine/cfproject
 > git --version # timeout=10
using GIT_SSH to set credentials 
 > git fetch --tags --progress ssh://jen...@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

[Mark Waite]

On Thu, Aug 21, 2014 at 1:43 PM, Wood Peter <peterw...@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.

--

Thanks!

Mark Waite

[Andy Wang]

Hi Peter,

Same thing happened to me as well. I'm using Jenkins-1.634; Git-Plugin-2.4.0; Git-Client-Plugin-1.19.0; Gerrit-trigger:2.16.0

I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.

On git plugin, I set Refspec to refs/changes/*:refs/changes/* and 'Branches to build' to $GERRIT_REFSPEC.

The job can be triggered when new patch set is created. However, the changelog to this build contains all the changes (max 1024 changes in total).

This issue bothers me a lot because I'm sending emails to all the people contributing to that changelog instead of the committer himself.

So I'm eager to know that if you had find out a solution to this issue? 

Thanks,

looking forward to your reply.

Andy

[Björn Pedersen]

Am Montag, 26. Oktober 2015 10:43:23 UTC+1 schrieb Andy Wang:

Hi Peter,

Same thing happened to me as well. I'm using Jenkins-1.634; Git-Plugin-2.4.0; Git-Client-Plugin-1.19.0; Gerrit-trigger:2.16.0

I configed the Gerrit Trigger plugin on jenkins based on the article https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger.

On git plugin, I set Refspec to refs/changes/*:refs/changes/* and 'Branches to build' to $GERRIT_REFSPEC.

Set  Refspec to $GERRIT_REFSPEC, branches to $GERRIT_BRANCH and make sure to use the gerrit trigger strategy under advanced options.
 
I guess the doc is just slighty outdated.

Björn

[Andy Wang]

Thanks. I set  Refspec to $GERRIT_REFSPEC, branches to $GERRIT_BRANCH and it didn't work for me. Then I changed the branch to origin/$GERRIT_BRANCH, it all worked. I guess that the $GERRIT_BRANCH only pass "master" to git plugin, and it need full branch name. 

Thanks again and this do solve my problem!