Commits since last build is wrong when last build commit no longer exists

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

XMLWordPrintable

      The "Commits since last build" shows 200 when it can not determine the commits since last build.

      Steps to reproduce:

      1. Push new branch with 1 commit
      2. Amend commit (replace commit) and force-push

      Instead of nothing or unable to determine, it shows 200 - which is wrong.

      • Commits since last build: 200

        1. Bildschirmfoto 2021-12-02 um 16.43.44.png
          Bildschirmfoto 2021-12-02 um 16.43.44.png
          54 kB

            Assignee:
            Unassigned
            Reporter:
            Jan Klass
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: