[JIRA] (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.
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164905.1441408158000.4695.1578484921450%40Atlassian.JIRA.
[JIRA] (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.
Title: Message Title 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) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
