-
Bug
-
Resolution: Unresolved
-
Minor
The "Commits since last build" shows 200 when it can not determine the commits since last build.
Steps to reproduce:
- Push new branch with 1 commit
- Amend commit (replace commit) and force-push
Instead of nothing or unable to determine, it shows 200 - which is wrong.
Commits since last build: 200
[JENKINS-67281] Commits since last build is wrong when last build commit no longer exists
Component/s | New: git-plugin [ 15543 ] | |
Component/s | Original: git-forensics-plugin [ 25321 ] |
Description |
Original:
The "Commits since last build" seems to show 2 * max-commits-to-evaluate value when it can not determine the commits since last build.
Steps to reproduce: # Push new branch with 1 commit # Amend commit (replace commit) and force-push Instead of nothing or unable to determine, it shows 200 - which is wrong. * {quote}Commits since last build: 200{quote} |
New:
The "Commits since last build" shows 200 when it can not determine the commits since last build.
Steps to reproduce: # Push new branch with 1 commit # Amend commit (replace commit) and force-push Instead of nothing or unable to determine, it shows 200 - which is wrong. * {quote}Commits since last build: 200 {quote} |
Component/s | New: git-forensics-plugin [ 25321 ] | |
Component/s | Original: git-plugin [ 15543 ] |
Attachment | New: Direkt_Depot_8013202984_Abrechnung_Kauf_IE00B8FHGS14_Order_157822027_001_20200204.pdf [ 56889 ] |
Attachment | Original: Direkt_Depot_8013202984_Abrechnung_Kauf_IE00B8FHGS14_Order_157822027_001_20200204.pdf [ 56889 ] |
I see now that this is probably not a forensics plugin issue, but git SCM instead.