-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Jenkins ver. 2.121.3
Git Changelog plugin version 2.16
git-client 2.7.0
git 3.7.1
The Git ChangeLog's are repeated in the builds as shown below example.
Note:
We are doing checkout of the previous revision to do the comparision of scripts.
But the changelog is set to false for the previous revision checkout.
Hence it shows multiple "Git Build Data". But Change log is repeating somehow for every next build executed, even though the next build is executed after 2 days.
Example ChangeLog
#12 (Jan 31, 2019 8:00:00 AM)
[JIRA-XXX]: Added validation — User3
[JIRA-XXX]: Code Clean up — User1
[JIRA-XXX]: Cleanup — User2
[JIRA-XXX]: State model and final cleanup - User1
#10 (Jan 28, 2019 8:00:00 AM)
[JIRA-XXX]: Added validation — User3
[JIRA-XXX]: Code Clean up — User1
[JIRA-XXX]: Cleanup — User2
#9 (Jan 27, 2019 8:00:00 AM)
[JIRA-XXX]: Added validation — User3
You mention that "changelog is set to false for the previous revision checkout". In what context is changelog set to false? For example, did you use a command like the following in your Pipeline:
or did you use the more verbose checkout syntax like this:
In the workflow scm step plugin README, it says:
Based on that text from the README, I would have assumed that your decision to set changelog to false means that the changelog is not being computed. If it is not being computed, then it may repeat or not repeat or be useful or not useful. If the changelog is important to you, why did you disable changelog generation?
Based on the phrasing of the bug report, I think you want this to be assigned to the workflow-scm-step plugin, rather than assigning it to core, git plugin, and workflow-scm-step plugins. However, I'm not entirely sure that is the case.
Is your concern about the duplication of the build data that is presented in the user interface for the job? In the example you gave, I assume that build 9 had completed before build 10 started, so you were expecting that "Added validation - User3" would not appear in the changelog for build 10 since it was already included in the completed and successful build 9.
Is your concern about the results in a change log generated by the git changelog plugin?
Please provide more details so that others can understand what you are expecting and how to duplicate the problem.