[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title
Mark Waite edited a comment on JENKINS-60064
Re: upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
The [MAX_CHANGELOG value|https://github.com/jenkinsci/git-plugin/blob/92b522f8a5673294f1e90040675649e6241d1c5e/src/main/java/hudson/plugins/git/GitSCM.java#L1901] in the plugin is used to limit the maximum number of changes which might be attributed to a single commit. Default value is 1024. Since computeChangeLog takes {{BuildData previousBuildData}} as an argument, I assume that the 4.0.0-rc plugin version was not recording BuildData, so the 4.0.0 plugin version attempted to report the entire history as a change in that build. The 1024 upper bound prevented it assigning the entire repository history to that build. I don't plan to attempt any fix to this bug. The git plugin 4.0.0-rc was a mistaken release that was blacklisted within two weeks of its release.
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.202897.1572976989000.12584.1573596000549%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Mark Waite resolved as Won't Fix Jenkins / JENKINS-60064 upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Change By: Mark Waite Status: Open Resolved Resolution: Won't Fix 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.202897.1572976989000.12586.1573596000582%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Mark Waite closed an issue as Won't Fix Jenkins / JENKINS-60064 upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Change By: Mark Waite Status: Resolved 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.202897.1572976989000.12588.1573596000655%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Mark Waite commented on JENKINS-60064 Re: upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit The MAX_CHANGELOG value in the plugin is used to limit the maximum number of changes which might be attributed to a single commit. Default value is 1024. Since computeChangeLog takes BuildData previousBuildData as an argument, I assume that the 4.0.0-rc plugin version was not recording BuildData, so the 4.0.0 plugin version attempted to report the entire history as a change in that build. The 1024 upper bound prevented it assigning the entire repository history to that build. 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.202897.1572976989000.12582.1573595940171%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60064 upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Change By: Mark Waite Assignee: Mark Waite 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.202897.1572976989000.9566.1572982020123%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Mark Waite commented on JENKINS-60064 Re: upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Please provide more information so that others can duplicate the problem. I've not seen such a problem. The 4.0.0-rc version of the git plugin removed BuildData tracking from inside the plugin and replaced it with another class. That change introduced too many incompatibilities, so it was reverted for 4.0.0-beta10 and later. BuildData handling in git plugin 4.0.0 is different than in git plugin 4.0.0-rc but is the same as BuildData handling in git plugin 3.x. The return to 3.x behavior was crucial to maintain compatibility with other plugins that depend on BuildData assigned by the git plugin. 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.202897.1572976989000.9564.1572981960215%40Atlassian.JIRA.
[JIRA] (JENKINS-60064) upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60064 upgrading git(client)plugin from 4.0.0rc/3.0.0rc to 4.0.0/3.0.0 resulted in 1024 changes being attributed to single commit Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin, git-plugin Created: 2019-11-05 18:03 Priority: Minor Reporter: Josh Soref We use github-branch-source-plugin to detect changes. Getting remote branch master... [Tue Nov 05 11:54:53 EST 2019] Received Push event to branch master in repository org/repo UPDATED event from 192.30.252.91 ⇒ https://jenkins/github-webhook/ with timestamp Tue Nov 05 11:54:48 EST 2019 11:54:53 Connecting to https://api.github.com using u...@example.com/** (User account for GitHub) Checking branch master Getting remote pull requests from branch master... ‘Jenkinsfile’ found Met criteria Changes detected: master (OLD-SHA → NEXT-SHA) This is what triggered the build. I checked github and confirmed, this is a single commit. Actual result: Both classic and blueocean show 1024 changes listed for the build instead of the expected single commit (NEXT-SHA).
