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

git skipping resolution of commit and fall back to main due to potential memory lead

XMLWordPrintable

      PR CI pick up the latest change of the feature branch failed with message like below

      git fetch --no-tags --force --progress – https://ado-org/_git/reponame +refs/heads/:refs/remotes/origin/ +refs/pull//merge:refs/remotes/origin/pull//merge # timeout=10

        skipping resolution of commit b42a8360549001d1ecaadb43dfaa8212c8354bf3,

            possible memory leak due to Git plugin usage

        and fallback to 63a0bfef2a0d0605cf7c89f66d339e0bc56f0408 (main)

       

      where the commit really should not be merged with the main branch.

       

      I'm wondering if this is the correct action, rather than exiting with an error and letting the system handle the memory leak itself. Or is there a workaround with the configuration?

            Unassigned Unassigned
            chengwc Jack
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: