Yes - native git works like a charm - thanks! Any idea if the jgit imp. will be fixed to address this?
2013/9/5 David Karlsen <davidkarl...@gmail.com> > Yeah - I'm left with some BOFH operating Jenkins - and it's installed on > an ancient RHEL5 box which have no git binaries. > We can compile it by hand (in fact I have) - but that results in having to > configure the path for the native git differently on the different boxes > (we have a fair amount of slaves). > I'll do some hacks on the PATH so git shows up in path and see how that > goes. > > Even though if I get this to work, we also have some more exotic slaves > running AIX, where it's not straightforward to get git in place (again > dependent on corporate BOFH). > > > 2013/9/5 Mark Waite <markwa...@yahoo.com> > >> I believe my testing of the Git plugin 2.0 beta confirmed that it was >> able to push back. However, I think it will be better for you if you stay >> with the released plugin and use command line Git rather than JGit as your >> executable. Is there a compelling reason you must use jgit? >> >> I recommend against Git plugin 2.0 beta for production work because it >> has other serious problems. For example: >> >> https://issues.jenkins-ci.org/browse/JENKINS-19043 - hangs "Updating >> references" with large repos >> https://issues.jenkins-ci.org/browse/JENKINS-18988 - exception fails >> checkout sometimes >> https://issues.jenkins-ci.org/browse/JENKINS-18960 - cloning large repo >> is dramatically slower >> https://issues.jenkins-ci.org/browse/JENKINS-19108 - fails to checkout >> specific branch >> https://issues.jenkins-ci.org/browse/JENKINS-19305 - shallow clone >> doesn't work >> https://issues.jenkins-ci.org/browse/JENKINS-19037 - error dialog in >> preference edits >> https://issues.jenkins-ci.org/browse/JENKINS-19036 - serialization >> errors on slaves >> https://issues.jenkins-ci.org/browse/JENKINS-18957 - null pointer >> exception >> >> The git plugin 2.0 beta jgit implementation is a significant improvement >> over the jgit implementation in git plugin 1.5.0, but I don't think it is >> ready for production yet. >> >> Mark Waite >> >> ------------------------------ >> *From:* David Karlsen <davidkarl...@gmail.com> >> *To:* jenkinsci-users@googlegroups.com >> *Sent:* Thursday, September 5, 2013 1:37 AM >> >> *Subject:* Re: Git push back changes >> >> Thanks! Would pushing work if I went for git-plugin 2.0 beta? >> >> >> 2013/9/5 Mark Waite <markwa...@yahoo.com> >> >> I think the key problem in that list is "using jgit executable". The >> jgit implementation in the current released Git plugin is not able to push >> to a central repository, along with many other limitations. >> >> You'll need to use the command line git implementation if you want to >> push back to a central repository. >> >> There are several other bugs related to the jgit implementation, if >> you're interested in them. Even the Git plugin beta 2.0 still seems to >> have a number of rough spots with the jgit implementation. >> >> Mark Waite >> >> ------------------------------ >> *From:* David Karlsen <davidkarl...@gmail.com> >> *To:* jenkinsci-users@googlegroups.com >> *Sent:* Wednesday, September 4, 2013 8:24 AM >> *Subject:* Re: Git push back changes >> >> My config: >> Repository url: >> http://username:credenti...@test.fswiki.evry.com:7990/scm/tac/tac-jfr-server.git >> name: stash >> branches to build: >> stash/topic/** >> stash/dev >> >> under 2nd advanced I have: >> Checkout/merge to local branch (optional): master (tried with and w/o >> value here) >> Config user.name Value: the userid >> Config user.email Value: the mail adr >> >> Merge options: >> merge before build is checked, >> name of repository: stash >> branch to merge to: master >> >> using jgit executable >> >> then under post build actions, I have, for the git publisher: >> Push Only If Build Succeed: checked >> merge results: checked >> branches: >> branch to push: master >> target remote name: stash >> >> from console log: >> >> Building on master in workspace /var/lib/jenkins/jobs/tac-jfr-srv/workspace >> Checkout:workspace / /var/lib/jenkins/jobs/tac-jfr-srv/workspace - >> hudson.remoting.LocalChannel@1b8223f2 >> Using strategy: Default >> Last Built Revision: Revision a8ea258e0efe1d514f31c2c4b5cc60ea6ed6b3c6 >> (stash/dev) >> Fetching changes from 1 remote Git repository >> Commencing build of Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 >> (stash/dev) >> Merging Revision d5b0609fcb1061ee658d971ef5bffb06c1d40646 (stash/dev) onto >> master >> >> ..... ok building >> >> Skipping Sonar analysis >> Pushing HEAD to branch master of stash repository >> Opening connection >> Counting objects >> Finding sources >> Writing objects >> Pushing HEAD to branch master at repo stash >> Opening connection >> Counting objects >> Finding sources >> Writing objects >> No emails were triggered. >> >> >> >> >> 2013/9/2 Mark Waite <markwa...@yahoo.com> >> >> The bug you referenced is fixed in the current versions of the git client >> plugin and the git plugin. I can confirm that Git plugin versions 1.4.0 >> and 1.5.0 are able to publish changes when used with git client plugin >> 1.1.2. >> >> Unfortunately, that probably doesn't help you, since there is still some >> reason that your publish attempt is failing. You'll need to do more >> investigating to understand why publish works for others and not in the >> case you're testing. >> >> Mark Waite >> >> ------------------------------ >> *From:* David Karlsen <davidkarl...@gmail.com> >> *To:* jenkinsci-users@googlegroups.com >> *Sent:* Monday, September 2, 2013 2:53 AM >> *Subject:* Git push back changes >> >> I'm having problems getting jenkins to push back the merged branch to >> origin repo. (everything else works but the push back to the repository). >> >> Looks like this issue: >> >> http://jenkins-ci.361315.n4.nabble.com/Git-publisher-fails-to-push-td4659177.html >> >> I'm running: >> -bash-3.2$ cat git-client/META-INF/MANIFEST.MF >> Manifest-Version: 1.0 >> Archiver-Version: Plexus Archiver >> Created-By: Apache Maven >> Built-By: jglick >> Build-Jdk: 1.7.0_25 >> Extension-Name: git-client >> Specification-Title: Utility plugin for Git support in Jenkins >> Implementation-Title: git-client >> Implementation-Version: 1.1.2 >> Group-Id: org.jenkins-ci.plugins >> Short-Name: git-client >> Long-Name: Jenkins GIT client plugin >> Url: http://wiki.jenkins-ci.org/display/JENKINS/Git+Client+Plugin >> Plugin-Version: 1.1.2 >> Hudson-Version: 1.480 >> Jenkins-Version: 1.480 >> Plugin-Dependencies: ssh-credentials:1.0 >> Plugin-Developers: Nicolas De Loof:ndeloof:nicolas.del...@gmail.com >> >> -bash-3.2$ cat git/META-INF/MANIFEST.MF >> Manifest-Version: 1.0 >> Archiver-Version: Plexus Archiver >> Created-By: Apache Maven >> Built-By: nicolas >> Build-Jdk: 1.6.0_31 >> Extension-Name: git >> Specification-Title: Integrates Jenkins with GIT SCM >> Implementation-Title: git >> Implementation-Version: 1.4.0 >> Group-Id: org.jenkins-ci.plugins >> Short-Name: git >> Long-Name: Jenkins GIT plugin >> Url: http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin >> Plugin-Version: 1.4.0 >> Hudson-Version: 1.448 >> Jenkins-Version: 1.448 >> Plugin-Dependencies: token-macro:1.5.1;resolution:=optional,multiple-s >> cms:0.2;resolution:=optional,git-client:1.0.6,parameterized-trigger:2 >> .4;resolution:=optional >> Plugin-Developers: Kohsuke Kawaguchi:kohsuke:,Nicolas De Loof:ndeloof: >> nicolas.del...@gmail.com >> >> >> on core 1.509.2 >> >> are there any workarounds? AFAIK I'm running the latest git plugins for >> latest LTS. >> >> -- >> -- >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >> -- >> 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. >> >> >> >> >> -- >> -- >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >> -- >> 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. >> >> >> >> >> -- >> -- >> David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen >> -- >> 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. >> > > > > -- > -- > David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen -- 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.
