Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: git-plugin
-
Labels:None
-
Similar Issues:
Description
in the edge case where a previous build's commit no longer exists in the repository (as when, for example, the repository is replaced), the comand
git whatchanged --no-abbrev -M --pretty=raw <nonexistent hash>..<current TARGET>
as executed by the git plugin will return the entire history of the repository, up to TARGET. This can use a lot of memory, and was causing a heapsize error for my slaves.
The plugin should probably check for the existence of the previous commit, and handle it's nonexistence more gracefully (perhaps force a wipe of the workspace? or fail with an error message suggesting the user wipe the workspace?)
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Resolution | Fixed [ 1 ] | |
Status | Open [ 1 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Workflow | JNJira [ 138997 ] | JNJira + In-Review [ 204908 ] |