On May 12, 2009, at 05:05, María G.L. wrote:
> 2009/4/29, Ryan Schmidt wrote:
>
>> On Apr 29, 2009, at 03:28, María G.L. wrote:
>>
>>> In SAP Systems we use JDI as our repository. When we need to
>>> transport applications from Development Server to Test or
>>> Prodution Servers, exists a tool (called Change and transport
>>> system, CTS) to do it, that JDI owned.
>>>
>>> My question is: Is there any Subversion tool for the applications
>>> transport? The client i use is Subclipse and it will be
>>> interesting to integrate it with Subclipse.
>>
>> I'm not aware of such a tool for Subversion, but I also don't know
>> what it means to transport an application, and I'm not familiar
>> with SAP or JDI. Perhaps you could elaborate on exactly what you
>> need such a tool to do.
>>
>> In Subversion, I think you would usually simply check out an
>> additional working copy when you need to deploy on an additional
>> server.
>
> Hi Ryan, maybe I didn't explain my problem correctly, I'm going to
> try it again and i wish you could help me.
>
> I wanted to know if exists any Subversion tool to deploy my
> application in different servers as i want.
>
> First, i want to deploy my application in a Development Server.
> But, later, i want to deploy the application in a Production Server.
> Is there any tool to automatize this?
You still didn't say what you mean by "deploy". If you just mean that
you want to get the files from Subversion to those servers, then
there are many options available. You could svn checkout or svn
export your code to a local machine and then ftp or scp or rsync them
to the remote development or production server. If your development
and production servers have the svn client installed, and if your
repository is accessible to those servers over the network, and if
you have shell or screen sharing access to them, then it can be even
easier: connect to the server via ssh or vnc or whatever method you
have, and just run "svn checkout your://repository/url" to get a copy
of the code, and then "svn update" it when necessary.
Assuming you have one of the above available to you, then you could
automate it further. For example, you could declare that when you
make a tag in your repository whose name follows a certain format,
then that tag should be automatically deployed to some server. In
this way, deploying to a particular server becomes as easy as
creating a tag in the repository. There is a post-commit hook script
which has been mentioned on this list many times to make that easy,
though I forget its name at the moment.... Maybe someone else will
remember what I'm talking about and post it again.
P.S: Use Reply All so your reply goes to the list too, not just to me.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2212873
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-05-12 15:07:31 CEST