I think you've found a bug in the Git publisher.  I see the same behavior after 
updating to Git client plugin 1.4.0 and Git plugin 1.3.0.  

Oddly, I think that the bug was not there in the Git plugin pre-release 
snapshot of 1.3.0 which I built on 2 March 2013.  That could indicate that the 
issue is in the Git client plugin, or that the issue was introduced between 2 
March 2013 and the release of the 1.3.0 Git plugin.

If you urgently need the Git publisher, you may want to consider using the 
"Advanced" tab in the plugins section to install Git plugin 1.1.26.  I believe 
that is the Git plugin version prior to the refactoring which created the Git 
client plugin.

Refer to https://issues.jenkins-ci.org/browse/JENKINS-16940 for a Git publisher 
issue with versions of the plugin from 1.1.27 to 1.2.0.  That issue seems to be 
resolved with 1.3.0, though 1.3.0 shows the bug you've discovered.

Thanks,
Mark Waite



>________________________________
> From: Patrick <petrikvanderve...@gmail.com>
>To: jenkinsci-users@googlegroups.com 
>Sent: Thursday, March 14, 2013 12:56 AM
>Subject: Git publisher fails to push
> 
>
>Hi All
>
>
>I've been trying to use the GIT publisher to push the changes from my 
>integration branch back to my origin/master branch (sort of like here: 
>http://twasink.net/2011/09/20/git-feature-branches-and-jenkins-or-how-i-learned-to-stop-worrying-about-broken-builds/).
> I've managed to get the GIT plugin to perform the necessary merging but I 
>can't get the publisher to push the data back into the origin/master. 
>
>
>The build log shows this:
>
>
>Checkout:workspace / F:\integration\jenkins\jobs\Utilities-Build\workspace - 
>hudson.remoting.LocalChannel@42d2821b
Using strategy: Default
Last Built Revision: Revision ae06698285dbe55d15849c1469173472a3a99d88 
(integration/gitpushtest)
Cloning the remote Git repository
Cloning repository D:\repository\utilities\code\integration
git --version
git version 1.8.0.msysgit.0 
>Commencing build of Revision ae06698285dbe55d15849c1469173472a3a99d88 
>(integration/gitpushtest)
Merging Revision ae06698285dbe55d15849c1469173472a3a99d88 
(integration/gitpushtest) onto master
>..
>..
>..
>..
>..
>Pushing HEAD to branch master of origin repository
Opening connection
Counting objects
Finding sources
Getting sizes
Compressing objects
Writing objects
Pushing HEAD to branch master at repo origin
Opening connection
Counting objects
Finding sources
Getting sizes
Compressing objects
Writing objects
>
>
>While in the log it seems that the changes get pushed back nothing shows up in 
>the origin/master branch.
>
>
>My settings are:
>Source code management: Git
>    Repository 1:
>
>        URL: D:\repository\utilities\code\integration
>        Name: integration
>
>
>    Repository 2:
>        URL: D:\repository\utilities\code\master
>        Name: origin
>
>
>    Branches to build: integration/**
>
>
>    Merge before build:
>        Name: origin
>        Branch: master
>
>
>Publisher:
>
>    Push only if build succeeds: selected
>    Merge results : selected
>
>
>    Branches:
>        branch: master
>        target: origin
>
>
>Can anybody shed any light on this issue?
>
>
>Thanks
>
>
>Petrik
-- 
>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 jenkinsci-users+unsubscr...@googlegroups.com.
>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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Reply via email to