HELP: ability to have a vcs source for monitoring and a different one for pulling code down.

Help

I am needing to deploy to an environment in a DMZ type of environment that requires a different URL: Port (442) for pulling code from our apache svn repo than the one needed for monitoring for changes.  The team city server sits in a non DMZ environment.  The subversion URL for monitoring for changes, is through a different machine name (ie, https://tnw2s-build/releases ) than the URL required on the build agent machine running in (DMZ Zone).  The DMZ zone URL uses a different machine name (https://lt-build:442/releases ) etc.

How can I tell Team City to monitor the local URL in the non dmz environment but pull code to the build agent using the dmz URL.  It seems like the VCS source is for both monitoring (triggering) and for pulling code to the buildagent machine in the DMZ.  If I set the VCS source to the DMZ subversion settings, I get a big "problem with VCS connection"  error.


Help

3 comments
Comment actions Permalink

OK I have figured a work around and that is to add the DMZ Zone machine name used for the SVN URL to the host file and point it to the non dmz machine name on the team city server.  This fakes out the team city server and allows using the DMZ machine name.

IDK if that makes sense as I am still here at work and my writing seems unclear.

0
Comment actions Permalink

Lance,

Using server-side checkout seems to be another available option in your case.

0
Comment actions Permalink

Thanks Yegor,

       We are needing to do the pulls (checkouts) on the dmz side for a good reason.  We were doing server side checkouts before and then we had to do secure transfer of files and the only thing we had avaiable was sftp. This was extremely slow.   Now with the build agent side checkouts, we can pull from an apache https server with subversion, where we have our build binaries checked in, and pull that across.

Thanks

0

Please sign in to leave a comment.