Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66885

Multibranch empty changes reported by scm but not by git plugin

      When running a multibranch pipeline job with a repository that commits a series of random messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

      Refer to the JENKINS-66885 multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

      Changes report non-empty commits

      Changes report in the UI of the multibranch job looks like this when commits are not empty:

      Changes report empty commits

      Changes report in the UI of the multibranch job looks like this when commits are empty:

      Individual job page with empty commits

      When the changes are not reported, still the "SCM" section shows that there were changes.

      The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

          [JENKINS-66885] Multibranch empty changes reported by scm but not by git plugin

          Mark Waite created issue -
          Mark Waite made changes -
          Attachment New: scm-counts-correctly.png [ 56551 ]
          Mark Waite made changes -
          Description Original: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          When the changes are not reported, still the "SCM" section shows that there were changes.
          New: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          .h1 Changes report empty vs. non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          .h1 Individual Job Page

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          Mark Waite made changes -
          Description Original: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          .h1 Changes report empty vs. non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          .h1 Individual Job Page

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          New: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report empty vs. non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual Job Page

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          Mark Waite made changes -
          Description Original: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report empty vs. non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual Job Page

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          New: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          h1. Changes report empty commits

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual job page with empty commits

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          Mark Waite made changes -
          Assignee Original: Mark Waite [ markewaite ]
          Mark Waite made changes -
          Description Original: When running a multibranch pipeline job that is configured with JGit and commits a series of random commit messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-36637-jgit multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          h1. Changes report empty commits

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual job page with empty commits

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          New: When running a multibranch pipeline job with a repository that commits a series of random messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-66885 multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          h1. Changes report empty commits

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual job page with empty commits

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          Mark Waite made changes -
          Description Original: When running a multibranch pipeline job with a repository that commits a series of random messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the JENKINS-66885 multibranch pipeline job in my jenkins-bugs repository for the experiments that were used to check this behavior.

          h1. Changes report non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          h1. Changes report empty commits

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual job page with empty commits

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!
          New: When running a multibranch pipeline job with a repository that commits a series of random messages with no changes in the files of the commits, the changes report shows only the commits that change file contents. Commits that do not change file contents are not displayed as changes by the git plugin though they are reported as changes by scm.

          Refer to the [JENKINS-66885 multibranch pipeline job in my jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-66885] for the experiments that were used to check this behavior.

          h1. Changes report non-empty commits

          Changes report in the UI of the multibranch job looks like this when commits are not empty:

           !when-commits-include-files.png|!

          h1. Changes report empty commits

          Changes report in the UI of the multibranch job looks like this when commits are empty:

           !when-commits-are-empty.png|!

          h1. Individual job page with empty commits

          When the changes are not reported, still the "SCM" section shows that there were changes.

          The summary page for the individual build shows the inconsistency very clearly. It reports one change yet in the "SCM" section

           !scm-counts-correctly.png|!

            Unassigned Unassigned
            markewaite Mark Waite
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: