[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: POST-commit hook issue - Check in works

From: Matt Parks <mparks_at_empowersis.com>
Date: Tue, 11 Feb 2014 10:14:16 -0500

Ben,

Set up a new Virtual Server for SVN yesterday, and now I have to re-write
my post-commit hook in some other DOS type language, instead of the bash
script I was using.

Just wanted to let you know, no resolution to issue, but moving to another
server may help.

Matthew C. Parks

*Consultant*

*EMPOWER Student Information System*

ComSpec International, Inc.

30800 Telegraph Rd, Ste 2775

Bingham Farms, MI 48025

PH: 248-647-8841 ext. 307

FX: 248-647-6961

*EMPOWER Student Information System for Higher Education - *
www.empowersis.com <http://www.empower-xl.com/>

*Custom Software Development Services - *www.comspec-intnl.com

On Mon, Feb 10, 2014 at 9:35 AM, Branko Čibej <brane_at_wandisco.com> wrote:

> On 10.02.2014 15:23, Matt Parks wrote:
>
> This is the error that the post-commit logs
>
> svn: OPTIONS of 'http://svnServer/svn/myREPO/trunk/wwwroot': could not
> connect to server (http://svnServer)
>
> If there is another log, I am not aware to look for it to share it here
> with you.
>
>
> So you're saying that when the checkout fails in the post-commit, nothing
> gets written to the Apache error log? If that's the case, then it doesn't
> even create a connection to your server; you're either using the wrong URL,
> or, for some reason, the host name is being resolved differently in your
> post-commit hook than when you try the same URL on the command line.
>
> I'm not aware of why that wouldn't work, unless you're storing the server
> name in an environment variable. The post-commit hook runs with an empty
> environment.
>
>
> -- Brane
>
>
> --
> Branko Čibej | Director of Subversion
> WANdisco // Non-Stop Data
> e. brane_at_wandisco.com
>
Received on 2014-02-11 16:14:52 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.