ruijterj that message will usually be followed by other messages that explain why command line git could not initialize the local repository. Failure to initialize a local repository is usually due to a problem with the local file system. It could be an ownership problem. It could be a permission problem. It could be a file system that is now mounted read-only. It could be a network file system that is offline.
That failure message looks like it will need a question and answer series to diagnose the failure. We use the Jenkins issue tracker for bugs and enhancements. We don't use it as a support forum.
We use https://community.jenkins.io and the Jenkins user mailing list and the Jenkins chat system for question and answer. There are more people reading those other locations than read the Jenkins issue tracker.
I'm closing this issue as "Not a defect". If the messages that you did not include in the report are not enough to tell you how to solve the problem, please start a conversation in one of the other locations. I'm confident that this is not an issue that is specific to git plugin 5.2.1. Git plugin 5.2.1 is being used in over 70,000 installations. It was released 2 months ago and is running many, many jobs on machines like ci.jenkins.io.
ruijterj that message will usually be followed by other messages that explain why command line git could not initialize the local repository. Failure to initialize a local repository is usually due to a problem with the local file system. It could be an ownership problem. It could be a permission problem. It could be a file system that is now mounted read-only. It could be a network file system that is offline.
That failure message looks like it will need a question and answer series to diagnose the failure. We use the Jenkins issue tracker for bugs and enhancements. We don't use it as a support forum.
We use https://community.jenkins.io and the Jenkins user mailing list and the Jenkins chat system for question and answer. There are more people reading those other locations than read the Jenkins issue tracker.
I'm closing this issue as "Not a defect". If the messages that you did not include in the report are not enough to tell you how to solve the problem, please start a conversation in one of the other locations. I'm confident that this is not an issue that is specific to git plugin 5.2.1. Git plugin 5.2.1 is being used in over 70,000 installations. It was released 2 months ago and is running many, many jobs on machines like ci.jenkins.io.