[JIRA] [git-plugin] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.

[matthewradams22@gmail.com (JIRA)]

Matthew Adams created an issue

Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build. Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 04/Sep/15 11:09 PM Environment: Jenkins 1.609.2 Git plugin 2.4.0 Priority: Minor Reporter: Matthew Adams If I push to source control in Stash and the hook notifies jenkins to build a job, it correctly shows the change log of only the commits since the last build. If i ever trigger the build manually from jenkins UI, the change log will show every change I have made since the last manual build (days, weeks or months worth of commits) Able to reproduce in many older version combos of jenkins/git as well like 1.592 and 2.2.2 Talked with Mark Waite about this briefly at JUC on 9/2 and it is believed to be a bug. Add Comment

This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)

[matthewradams22@gmail.com (JIRA)]

Matthew Adams updated an issue

Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.

Change By: Matthew Adams

If I push to source control in Stash and the hook notifies jenkins to build a job, it correctly shows the change log of only the commits since the last build. If i ever trigger the build manually from jenkins UI, the change log will show every change I have made since the last manual build (days, weeks or months worth of commits)    Able to reproduce in many older version combos of jenkins/git as well like 1.592 and 2.2.2    Talked with Mark Waite about this briefly at JUC on 9/2 and it is believed to be a bug. Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-30316

Re: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build. Can you provide more details about the job configuration and preferably a job definition and a public repo which shows the problem? I've not seen the problem on other jobs, so don't know how to duplicate it without your job definition or a set of steps to define the job.

Add Comment

[matthewradams22@gmail.com (JIRA)]

Matthew Adams commented on JENKINS-30316

Re: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of sine last build.

For me it happens with every job. I just made a new job with a echo shell script and give it a git repo and then set up the hook in stash to notify on commits. Perhaps it is a stash hook problem?

Add Comment

[matthewradams22@gmail.com (JIRA)]

Matthew Adams updated an issue

Jenkins / JENKINS-30316

Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build. Change By: Matthew Adams Summary: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of  sine  since  last build.

Add Comment

[matthewradams22@gmail.com (JIRA)]

Matthew Adams edited a comment on JENKINS-30316

Re: Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build. For me it happens with every job. I just made a new job with  a  aa  echo shell script and give it a git repo and then set up the hook in stash to notify on commits. Perhaps it is a stash hook problem?

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-30316

I can't duplicate the problem

Jenkins / JENKINS-30316

Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build.

Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite updated JENKINS-30316

Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build.

Change By: Mark Waite Status: Fixed but Unreleased Closed

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)