-
Bug
-
Resolution: Unresolved
-
Major
-
None
When the said option is used, the BuildData object associated with the build incorrectly indicates a commit before a merge, not the commit as a result of the merge, which was actually built.
[JENKINS-10764] When the pre-build merge option is used, build record indicates incorrect commit ID
Workflow | Original: JNJira [ 140966 ] | New: JNJira + In-Review [ 175383 ] |
Assignee | Original: Andrew Bayer [ abayer ] |
Example log indicating the problem. In this log, 01f4f7b55b5c60160e1c45f1dacb84bb5324f159 is chosen for the revision to build, then it get smerged with 01f4f7b55b5c60160e1c45f1dacb84bb5324f159 because of the pre-build merge option, and the merge produced a0e1a0913ace04a5ae96f8b7721ea70ed5b560dd.
In this case, BuildData should record a0e1a0913ace04a5ae96f8b7721ea70ed5b560dd, not 01f4f7b55b5c60160e1c45f1dacb84bb5324f159.