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

"Scan Multibranch Pipeline Now" does not scan for changes in externals

    Details

    • Similar Issues:

      Description

      Upon scanning, the plugin only checks the revision of the main directory of the trunk and branches, see partial log here:

      Checking directory /Jenkins/foo_main_project/branches@34
      
      Checking candidate branch /Jenkins/foo_main_project/trunk@95
            ‘Jenkinsfile’ found
      Met criteria
      No changes detected: trunk (still at 95)

      When commiting changes to externals within some subdirectory, the revision number of the trunk or the branch will not change. Thus it is necessary to check the revision numbers of trunk, branches and all externals within those.

       

        Attachments

          Activity

          There are no comments yet on this issue.

            People

            • Assignee:
              Unassigned
              Reporter:
              rfunke Rafael Funke
            • Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated: