Git plugin does not correctly record built revision on failed merge

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      If the plugin has to merge with multiple branches, and at least 1 merge succeeds and 1 fails, then the revision of the last successful merge is recorded as lastBuiltRevision, but not the original (marked) revision. Because the original revision is not recognized as already built, polling will trigger another build, resulting in an infinite loop.

            Assignee:
            Wannes Sels
            Reporter:
            Wannes Sels
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: