Jenkins change set entries can contain empty commitIds
Description
Environment
Use of a Jenkins SCM plugin that leaves the commitId empty
Activity
Show:
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Unassigned
UnassignedReporter

Story Points
3
Fix versions
Affects versions
Priority
Zoom
Open Zoom
Created June 25, 2018 at 6:11 PM
Updated June 26, 2018 at 8:28 AM
Resolved June 26, 2018 at 8:28 AM
Zoom
No all the source control plugins developed for Jenkins set the commitId field for a change set entry.
Currently the JSON Parser for change sets assumes that the commitId field is set, and if its not, then any existing comment message will not be parsed and not be used in the issue identification process.
This bug should be resolved in either allowing empty commitIds or the generation of these ids when they are missing.