Thanks so much.

        -----Original Message----- 
        From: [email protected] on behalf of Robert Hunter 
        Sent: Tue 9/12/2006 10:16 AM 
        To: [email protected] 
        Cc: 
        Subject: [Trac] Re: Commiting Code through SVN
        
        


        On Tue, 2006-09-12 at 09:01 -0400, Geri Rizzuto wrote:
        > I have a question on how code gets to the IIS server when code is 
committed.
        >
        > The developer that implemented the Trac/SVN systems is no longer with 
our
        > organization and we cannot determine how to get the committed code to 
the
        > IIS server.
        >
        > We can see that when we commit code through SVN, the source
        > module is wriiten to the trunk. Is there an automated process taht can
        > be set up to then copy that code to the development IIS server?
        
        If I understand you correctly, it's not *that* much trouble to set up
        what you want -- but it will some scripting knowledge as well
        as knowledge of IIS permissions.
        
        As far as I can tell, based on your description, your situation is
        something like the following:
        
         * You have a Web application or static Web site running on IIS.
         * You have a "development" IIS server which runs the latest
           development version of this Web application.
         * You manage the source code for this Web application with Subversion.
         * You use Trac for tracking development activity for
           the Web application.
         * Developers check out a working copy of trunk from the Subversion
           repository, and use that to develop the software.
         * Developers commit their changes to the Subversion trunk.
         * You want those changes to run on the "development" IIS server.
        
        If the above is true (or close enough), then you probably want
        to implement a "post-commit hook" for the Subversion repository.
        It also means that Trac has nothing to do with the problem or
        the solution -- it's just Subversion.
        
        It's a common enough case to be in the Subversion FAQ:
          http://subversion.tigris.org/faq.html#website-auto-update
        
        Note that the FAQ entry mentions some of the issues you might
        face, but presents solutions that work for Unix and Apache.
        
        --
        Rob Hunter
        
        
                
        
        


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/trac-users
-~----------~----~----~----~------~----~------~--~---

<<inline: winmail.dat>>

Reply via email to