withCredentialswrapper to call
git clonedirectly if you need a bare clone of a git repository. The use case is too specialized to add to the git plugin for over 250 000 installations
Aand then add one or more commits to branch
A, then the next time I run the job, the build will contain the "information" from before the commits were added. I tried the "clean before checkout" and "clean after checkout", but they didn't work. The only way I found to work around this is by using the "Wipe out workspace and force clone". The repository takes about 5 minus to clone, so I was hope to avoid that is possible.
JGit fails to checkout repository with submodules if the recursive option is set. The Javadoc is interesting:
at org.jenkinsci.plugins.gitclient.JGitAPIImpl.setupSubmoduleUrls(JGitAPIImpl.java:2530) at hudson.plugins.git.extensions.impl.SubmoduleOption.onCheckoutCompleted(SubmoduleOption.java:146) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1379) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:125)
--recurse-submodules. That would allow users to ignore the ugly mess inside the git plugin where it is opening and reading submodule configuration files from the local workspace.
remoteTrackinghere but nothing related to recursive checkout: https://github.com/jenkinsci/git-client-plugin/blob/master/src/main/java/org/jenkinsci/plugins/gitclient/UnsupportedCommand.java#L160
$ mvn clean verify # Want to assure that all tests pass locally before starting work $ mvn clean -DskipTests install # Want to create a git.hpi that can be installed on Jenkins $ mvn clean -DskipTests compile # Want to compile code so that I can start work in the IDE $ mvn clean -DskipTests hpi:run # Want to run Jenkins interactively with the plugin installed $ mvn clean -Djenkins.version=2.271 hpi:run # Want to run most recent Jenkins weekly with the plugin installed
$classwhen that pull request is ready