[JIRA] (JENKINS-55875) Submodule update fails when the submodule isn't clean

[rich...@whiuk.com (JIRA)]

Title: Message Title

Richard Whitehouse created an issue   Jenkins / JENKINS-55875 Submodule update fails when the submodule isn't clean Issue Type: Bug Assignee: Richard Whitehouse Components: git-client-plugin, git-plugin Created: 2019-01-30 20:00 Priority: Minor Reporter: Richard Whitehouse Jenkins doesn't forcibly update submodules. This means that a checkout can fail with: hudson.plugins.git.GitException: Command "git submodule update --init --recursive modules/gmock" returned status code 1: stdout: stderr: error: Your local changes to the following files would be overwritten by checkout: build-aux/config.guess build-aux/config.sub gtest/build-aux/config.guess gtest/build-aux/config.sub Please, commit your changes or stash them before you can switch branches. Aborting Unable to checkout 'ec44c6c1675c25b9827aacd08c02433cccde7780' in submodule path 'modules/gmock' Note, while JENKINS-22510 is relevant, and cleaning the checkout before checking out would resolve the problem, that's not a viable solution. Cleaning the checkout throws away all built files, which means the build is no longer incremental. Note, this behaviour makes Jenkins's behaviour for submodules match it's behaviour for the standard checkout (which is checked out with --force).   Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.