How to set upp a folder holding the currently released code version
19 views
Skip to first unread message
Alsterwasser
Jan 25, 2018, 4:15:53 PM1/25/18
to TortoiseSVN
Hello,
I'm quite a newbie on the area of tortoisesvn. I think I have understood the concept but I have not found the answer on the following question:
We are two colleges programming scripts for others in our company. We want to use tortoisesvn to keep control on different versions of course. Until now the users of our scripts have launched a main script we provided (with no real version control).
In tortoisesvn there is eg the working directory (with the checked out files) and the repository (with the history). Is there a kind of "released" folder to which I can guide users where they always will find the currently stable released versions of the scripts?
Kind regards
ak
I'm quite a newbie on the area of tortoisesvn. I think I have understood the concept but I have not found the answer on the following question:
We are two colleges programming scripts for others in our company. We want to use tortoisesvn to keep control on different versions of course. Until now the users of our scripts have launched a main script we provided (with no real version control).
In tortoisesvn there is eg the working directory (with the checked out files) and the repository (with the history). Is there a kind of "released" folder to which I can guide users where they always will find the currently stable released versions of the scripts?
Kind regards
ak
Niemann, Hartmut
Jan 26, 2018, 2:38:20 AM1/26/18
to TortoiseSVN
Hello ak!
You can do that, but you have to do that yourselves. (It's not hard)
You will probably have your development area, and there will be the "public" area for the scrips the colleagues should use.
As read access can not be controlled very fine-grained, I would suggest that the public space be a separate SVN project.
So set up a SVN project "public tools" and give all colleagues read access and have them check out a working copy on a defined place.
If you have a new version to deploy, copy it to your working copy of that public project, do some final tests and commit.
All your colleagues have to do is to update their working copy and they'll always have the latest version.
In my company we distribute programs with svn like this with huge success.
What took days to set up two years ago now takes about 15 minutes until a new PC is up and ready with all software we need.
Mit freundlichen Grüßen
Dr. Hartmut Niemann
Siemens AG
Mobility Division
MO RS LM EN CCI SRD
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Mobil: +49 173 5342327
mailto:hartmut...@siemens.com
www.siemens.com/ingenuityforlife
-----Ursprüngliche Nachricht-----
Von: Alsterwasser via TortoiseSVN [mailto:tortoisesvn+APn2wQe2BM-l2n9tqNe0...@googlegroups.com]
Gesendet: Donnerstag, 25. Januar 2018 21:33
An: TortoiseSVN
Betreff: How to set upp a folder holding the currently released code version
--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c8217a4d-297a-4c70-b4b8-afc9ed40a45d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You can do that, but you have to do that yourselves. (It's not hard)
You will probably have your development area, and there will be the "public" area for the scrips the colleagues should use.
As read access can not be controlled very fine-grained, I would suggest that the public space be a separate SVN project.
So set up a SVN project "public tools" and give all colleagues read access and have them check out a working copy on a defined place.
If you have a new version to deploy, copy it to your working copy of that public project, do some final tests and commit.
All your colleagues have to do is to update their working copy and they'll always have the latest version.
In my company we distribute programs with svn like this with huge success.
What took days to set up two years ago now takes about 15 minutes until a new PC is up and ready with all software we need.
Mit freundlichen Grüßen
Dr. Hartmut Niemann
Siemens AG
Mobility Division
MO RS LM EN CCI SRD
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Mobil: +49 173 5342327
mailto:hartmut...@siemens.com
www.siemens.com/ingenuityforlife
-----Ursprüngliche Nachricht-----
Von: Alsterwasser via TortoiseSVN [mailto:tortoisesvn+APn2wQe2BM-l2n9tqNe0...@googlegroups.com]
Gesendet: Donnerstag, 25. Januar 2018 21:33
An: TortoiseSVN
Betreff: How to set upp a folder holding the currently released code version
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c8217a4d-297a-4c70-b4b8-afc9ed40a45d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
alster...@googlemail.com
Jan 27, 2018, 1:45:29 PM1/27/18
to TortoiseSVN
Thank you for the tip to use a second svn project to solve this "issue". Never came to my mind to use a second project...... :-)
I'll try it out !
Cheers
ak
Reply all
Reply to author
Forward
0 new messages