windows - CruiseControl.NET Service / Subversion - Unable to connect to remote repository -


As a long time on the SO, I cruise control. NAT, I am making a round of questions with a difficult topic about subversion. , And a remote store. Here's the problem:

Using Apache 2.2.14 as a gateway to enable port 80 and 443 access, take a remote Subversion 1.6.6 repository running on remote server - We redirect the port to secure unencrypted traffic, and we have a well-configured SSL layer running with a self-signed certificate. All this works - I can point out a browser from my local machine (XP SP2 or Server 2008 SP2) in this repository, without certification verification, can painlessly certify against the repository ACL and I can see the stuff there. Equally, SVN commands that work on my local machine (either on the commandline or through TortoiseSVN) work.

Now cruise control on. Add 1.4.4.83 - Running with a simple script for a moment on my local machine Drag some source code from the remote repository, and build a very basic application This script works perfectly against local repositories , So only the difference is the subversion URL, which is now pointing to the remote server.

If I run CCNET in the command line shell (ccnet.exe), under my own account, it works.

If I run CC.NET as a service (ccservice.exe) however, it fails; By default, it runs as LOCALSERVICE, but I have already changed it to run with my credentials In this mode, the Subvarsian command issued first (SVN log) fails, complains That he can not connect to the server

I have spent good time checking it in four or five days; I know that this is not a firewall-type problem, because one commandline of CCNET issues works in the shell, and of course I can connect to remote servers via TortoiseSVN and a browser. It is not in SSL and / or certificate, as I have already imported the certificate - and then, it works fine in manual mode using TortoSSEN, a browser or SVN commands on the command line. This is not a DNS resolution issue, because I can specify the actual IP address of the remote server, and it still fails to connect - but definitely connects properly if I run in commandline mode ... < / P>

Also to see if something is going awkward, download it and watch it through CC.NET source code. As far as I can see, the only difference in the issue of issuing commands while running in service-mode is that an olloconosol call has been prepared to produce the console to process the subversion command, when they are born.

The best estimate I can make, at this level, is that the AllocConsole session is basically different from the standard command line session in any way - in that, even if the service runs under my user credentials Anyway, 'proper' network access in AllocConsole, however, there is not enough information about the Olococcool or CC.NET source code to be able to prove me all this, and so I am at a stalemate.

At the moment, I cc. Net running in commandline mode; However, it only feels unsatisfactory, because we prefer to run in service mode (which works against repositories in our local domain) to create a fixed work to start it when the machine starts to avoid the requirement. .

> Anyone got any suggestions? It was not a firewall problem, it was a proxy problem, it was broken.

We use BluCot here (yes, I know, I do not have a call) and therefore the subversion 'server' file, which is' C: \ Documents and Settings \ All User \ Application Data \ Subversion "There is an entry on all our developer PCs so that we can bypass the proxy for specific external treasures. However, we mostly use TortoiseSVN, and access this file through an asset sheet - so far, it does not know that it is a subversion file, not a TortoiseSVN file.

Naturally, because we have never messed up with the 'server' file on TortoiseSN Build Server, however, now Cruise Control. The Net needs to reach an external store (first it has only talked to our internal treasures), it was not able to get it before the Blue Rock roadblock.

Once the puzzle was found, I created a 'server' file on the build box, added our bypass configuration to it, and suddenly the Cruise Control. Subvision can see remote repositories in net and service mode.

I still can not believe why it worked in commandline mode but not service mode, but I have decided to do this so I am happy. :)


Comments

Post a Comment