Thanks, that fixes the security failure. It still seems gerrit functionality is broken.
I trigger a build event (Query and Trigger Gerrit Patches). The build starts, and before the data has even arrived, it's stamped 'Git Build Data' with a totally incorrect SHA1 for the build. The gerrit variables are all correct, particularly $GERRIT_PATCHSET_REVISION = correct SHA1 $GERRIT_REFSPEC = refs/changes/65/4465/2 I'd have thought setting Name : origin Refspec : $GERRIT_REFSPEC Branches to build: $GERRIT_PATCHSET_REVISION Choosing strategy : default would do the trick, but it seems to obsessively re-build a random (seemingly the first alphabetical) branch. On Tue, Oct 29, 2013 at 10:39 AM, nicolas de loof <nicolas.del...@gmail.com>wrote: > This is fixed in HEAD, try using a SNAPSHOT build for git-client > > > 2013/10/29 Nigel Magnay <nigel.mag...@gmail.com> > >> So, doing some digging : >> >> I can no longer use 'native' git, it blows up with the eventual cause: >> >> Caused by: >> java.lang.NullPointerException<http://stacktrace.jenkins-ci.org/search?query=java.lang.NullPointerException> >> >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:894)<http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials&entity=method> >> >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:52)<http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400&entity=method> >> >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:296)<http://stacktrace.jenkins-ci.org/search/?query=org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute&entity=method> >> >> ... 11 more >> >> ERROR: null >> >> >> Which looks like it can't find a RemoteAgentFactory to fire up the SSH. >> Which is odd. >> >> jgit also fails, but I suspect this might be down to the refspec, which >> should be something like refs/changes/65/4465/2 (or $GERRIT_REFSPEC) >> >> I've abandoned the gerrit choosing strategy, since it just seems to check >> out HEAD (which seems a little odd, but that doesn't mean it's not right). >> >> >> >> >> On Mon, Oct 28, 2013 at 1:51 PM, Mark Waite <mark.earl.wa...@gmail.com>wrote: >> >>> In case it matters, my problem configuration is a Windows 8 machine. >>> The Windows Server 2011 machine that is also in that configuration does >>> not show the problem, nor do any of the Debian Linux machines that are in >>> the configuration. >>> >>> Mark Waite >>> >>> >>> On Mon, Oct 28, 2013 at 7:49 AM, Mark Waite >>> <mark.earl.wa...@gmail.com>wrote: >>> >>>> I've seen a similar message in one of my git plugin 2.0 test >>>> configurations without using the Gerrit trigger. One of my jgit trivial >>>> test jobs was passing happily (though executing more builds than it should >>>> due to https://issues.jenkins-ci.org/browse/JENKINS-20286), when it >>>> suddenly began reporting that a SHA1 was missing. >>>> >>>> That report only happens on one of the configurations in the >>>> multi-configuration job, and it only happens on the multi-configuration job >>>> which uses jgit and uses a custom SCM name. The Jenkins instance has very >>>> few other plugins installed, and has never interacted with a Gerrit >>>> instance. >>>> >>>> I don't have time to investigate the conditions which cause the bug >>>> now, but hope within the next 24 hours to do some further investigation. >>>> >>>> Thanks, >>>> Mark Waite >>>> >>>> >>>> On Mon, Oct 28, 2013 at 7:36 AM, Nigel Magnay >>>> <nigel.mag...@gmail.com>wrote: >>>> >>>>> I'm not sure -- it's not the SHA1 that should be built (it's not the >>>>> ID of the SHA1 of the change set). >>>>> >>>>> It feels like jenkins is asking gerrit for a SHA that doesn't exist >>>>> (or perhaps - does not exist any longer, as it's been GCed out of the >>>>> gerrit repo). >>>>> >>>>> The git plugin also seems to be stamping a SHA1/id into the build >>>>> (sometimes multiple times!) that has nothing to do with the values it >>>>> should be using. >>>>> >>>>> https://issues.jenkins-ci.org/browse/JENKINS-20225 suggests I'm not >>>>> the only one suffering. I may have to resort to checking out the source >>>>> again :-// >>>>> >>>>> >>>>> >>>>> >>>>> On Mon, Oct 28, 2013 at 1:07 PM, Mark Waite <mark.earl.wa...@gmail.com >>>>> > wrote: >>>>> >>>>>> Does it succeed with the command line git provider, or is it failing >>>>>> with both command line and jgit? >>>>>> >>>>>> I thought "missing commit" usually meant that the git repository was >>>>>> corrupt and needed to be rebuilt. >>>>>> >>>>>> Which of the repositories contain that SHA1? (Is it in the Gerrit >>>>>> repo and not in the Jenkins repo, or vice versa)? >>>>>> >>>>>> Mark Waite >>>>>> >>>>>> >>>>>> On Mon, Oct 28, 2013 at 7:01 AM, Nigel Magnay < >>>>>> nigel.mag...@gmail.com> wrote: >>>>>> >>>>>>> Has anyone got the above combination to work? >>>>>>> >>>>>>> Our jenkins seems obsessed with building wrong versions. I'm not >>>>>>> sure which of the vague "Usage with the Git plugin" options (here >>>>>>> https://wiki.jenkins-ci.org/display/JENKINS/Gerrit+Trigger) are >>>>>>> valid, and our gerrit server is spitting errors such as: >>>>>>> >>>>>>> [2013-10-28 12:58:36,274] ERROR com.google.gerrit.sshd.BaseCommand : >>>>>>> Internal server error (user jenkins account 1000001) during >>>>>>> git-upload-pack >>>>>>> '/realtime' >>>>>>> >>>>>>> org.eclipse.jgit.transport.UploadPackInternalServerErrorException >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.transport.UploadPack.sendPack(UploadPack.java:1041) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.transport.UploadPack.service(UploadPack.java:612) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.transport.UploadPack.upload(UploadPack.java:521) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.sshd.commands.Upload.runImpl(Upload.java:57) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.sshd.AbstractGitCommand.service(AbstractGitCommand.java:101) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.sshd.AbstractGitCommand.access$000(AbstractGitCommand.java:32) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.sshd.AbstractGitCommand$1.run(AbstractGitCommand.java:70) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.sshd.BaseCommand$TaskThunk.run(BaseCommand.java:429) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) >>>>>>> >>>>>>> at java.util.concurrent.FutureTask.run(FutureTask.java:138) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:98) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:206) >>>>>>> >>>>>>> at >>>>>>> com.google.gerrit.server.git.WorkQueue$Task.run(WorkQueue.java:337) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) >>>>>>> >>>>>>> at >>>>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) >>>>>>> >>>>>>> at java.lang.Thread.run(Thread.java:662) >>>>>>> >>>>>>> Caused by: org.eclipse.jgit.errors.MissingObjectException: Missing >>>>>>> commit 58d4ae5cb97e1a946f8ddeb168baaa6d781c7775 >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.internal.storage.file.WindowCursor.open(WindowCursor.java:149) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.revwalk.RevWalk.getCachedBytes(RevWalk.java:853) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.revwalk.RevCommit.parseHeaders(RevCommit.java:142) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.revwalk.PendingGenerator.next(PendingGenerator.java:148) >>>>>>> >>>>>>> at org.eclipse.jgit.revwalk.RevWalk.next(RevWalk.java:414) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.revwalk.ObjectWalk.next(ObjectWalk.java:261) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.internal.storage.pack.PackWriter.findObjectsToPack(PackWriter.java:1753) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.internal.storage.pack.PackWriter.preparePack(PackWriter.java:797) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.transport.UploadPack.sendPack(UploadPack.java:1150) >>>>>>> >>>>>>> at >>>>>>> org.eclipse.jgit.transport.UploadPack.sendPack(UploadPack.java:1035) >>>>>>> >>>>>>> ... 16 more >>>>>>> >>>>>>> >>>>>>> Which is odd, as that's not the SHA1 the change set is trying to >>>>>>> build... >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> 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. >>>>>> >>>>> >>>>> -- >>>>> 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. >>> >> >> -- >> 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. > -- 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.
