-
Bug
-
Resolution: Duplicate
-
Minor
-
Jenkins on AL2023 EC2 m6a.4xlarge with EFS
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?
- is duplicated by
-
JENKINS-19022 GIT Plugin (any version) heavily bloats memory use and size of build.xml with "BuildData" fields
-
- Open
-