That really needs to be fixed; if include/exclude specifications cannot be processed without "Force polling using workspace", then the plugin should just turn that on itself. Allowing the user to select options that will never result in a working configuration is user-hostile.
If at some point in the future remote polling can be done without a workspace then the plugin could stop overriding the 'force workspace' option. ----- Original Message ----- From: [email protected] To: [email protected] At: Jan 5 2014 22:30:24 That stack trace looks a lot like https://issues.jenkins-ci.org/browse/JENKINS-20258 . You might consider removing the "prune branches" option from the job configuration to see if that helps avoid the problem. If you're using include region, exclude region, or exclude user, then you'll need to also add the "Force polling using workspace" option. The default is now to use fast remote polling, but that default cannot process include or exclude regions. Mark Waite On Sun, Jan 5, 2014 at 7:12 PM, Jon Schewe <[email protected]> wrote: Anyone else running into problems with the git plugin version 2.0? I'm using Jenkins 1.509.4 and have run into the problem that if I wipe out my workspace either manually that the plugin can't clone a new workspace. It errors like this: 16:08:58 Started by user Jon Schewe 16:08:58 Building in workspace /home/hudson/.hudson/jobs/fll-sw-feature-branches/workspace 16:08:58 Pruning obsolete local branches 16:08:58 FATAL: Command "config --get remote.origin.url" returned status code 1: 16:08:58 stdout: 16:08:58 stderr: 16:08:58 hudson.plugins.git.GitException: Command "config --get remote.origin.url" returned status code 1: 16:08:58 stdout: 16:08:58 stderr: 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:981) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:961) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:957) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:877) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:887) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.getRemoteUrl(CliGitAPIImpl.java:615) 16:08:58 at hudson.plugins.git.GitAPI.getRemoteUrl(GitAPI.java:61) 16:08:58 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.prune(CliGitAPIImpl.java:405) 16:08:58 at hudson.plugins.git.extensions.impl.PruneStaleBranch.beforeCheckout(PruneStaleBranch.java:31) 16:08:58 at hudson.plugins.git.GitSCM.checkout(GitSCM.java:858) 16:08:58 at hudson.model.AbstractProject.checkout(AbstractProject.java:1376) 16:08:58 at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:655) 16:08:58 at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) 16:08:58 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) 16:08:58 at hudson.model.Run.execute(Run.java:1592) 16:08:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 16:08:58 at hudson.model.ResourceController.execute(ResourceController.java:88) 16:08:58 at hudson.model.Executor.run(Executor.java:237) Sometimes clearing the SCM configuration and then setting it again works, but that isn't working for me right now either. Also switching to the inverse choose strategy doesn't appear to work like it used to. Instead the master branch was built rather than being the branch to exclude. I've manually cloned my repository into the workspace directory and that seems to have gotten me building again, although the inverse build strategy still isn't working. -- http://mtu.net/~jpschewe -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
