Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Ubuntu Lucid
Description
Version 1.1.6 works as expected. 1.1.8 now fails when running git remote prune. It might be significant that the repository in question is the preview server Git publisher pushes to and not the origin.
Checkout:workspace / /var/lib/jenkins/jobs/proj-trunk/workspace - hudson.remoting.LocalChannel@5240f1d3 Using strategy: Default Last Built Revision: Revision 51113a2f81f67645291ca381a8bc32f5cb0ebf47 (origin/master) Checkout:wdl / /var/lib/jenkins/jobs/proj-trunk/workspace/wdl - hudson.remoting.LocalChannel@5240f1d3 Pruning obsolete local branches FATAL: Error performing command: git remote prune platinum Command "git remote prune platinum" returned status code 128: fatal: 'platinum' does not appear to be a git repository fatal: The remote end hung up unexpectedly hudson.plugins.git.GitException: Error performing command: git remote prune platinum Command "git remote prune platinum" returned status code 128: fatal: 'platinum' does not appear to be a git repository fatal: The remote end hung up unexpectedly
This account uses SSH public-key auth and works normally in all other cases, including after reverting to 1.1.6.
Integrated in
plugins_git-plugin #129
[FIXED JENKINS-9661] Added a check to make sure we actually have the remote defined locally before we prune it.
Andrew Bayer : d6dc41c4992adeea20cc385e5681b770ea57f01c
Files :