Repo Build Code Changes not Identified When Job Config is Modified

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

XMLWordPrintable

      It seems that every time a build job configuration is modified, the code list changes cannot be identified for the first build after the modification.

      The Jenkins repo plugin seems to be failing to properly parse and record all the changes that trigger a build. Either that or not all commits are showing up in the log

      In place of changes, the message 'Failed to determine' is displayed with a link to the log. Looking at the log does not reveal any errors or stack traces.

            Assignee:
            Unassigned
            Reporter:
            rejesi
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: