Mark Breen
marklbreen at gmail.com
Mon Jun 1 17:51:51 CDT 2009
Hello Shamil, I am trying to get some advice from the SVN forums on how to properly manage a private / public server environment which is what we have. When I start to get some results on it, I will offer to attempt to help here. However, before we start that, does the team still want to maintain the private / public source control servers. If so, I will try to get scripts written to automate a release from private to public, but if you are considering switching back to a codeplex only store, then I do not need to write such scripts. It is up to you all to let me know what is best for the team, Shamil, do I get it right that the main problem with the codeplex only environment is that codeplex does not allow certain users to lock files? And do I have it right that you wish to lock the proj files to avoid people messing them up with the have earlier builds? In that case I guess that you must have been maintaining the latest / most correct proj file for the team? Is that right? Actually as I write this email, I realise that I am attempting to assist in solving a problem, but I am not 100% sure I know what the problem really is. I recall it was related to the proj and sln files, but would you like to remind me what the problem was and what you did to over come the problem. I will then try to help, if that help is needed. thanks Mark 2009/5/29 Salakhetdinov Shamil <mcp2004 at mail.ru> > Hello Mark, > > No, I didn't try to use export feature of TortoiseSVN: to publish on > CodePlex we have to get all the source files from latest copy of you server > sources, copy/replace them into local SVN folder of CodePlex (it will have > different files' versions numbers), add all new files to the .svn > descriptors and then submit that new version to CodePlex. AFAIU that should > be doable using SVN commands/scripts/batches but I'm not sure how to make it > 100% safe to add new files' types using such scripts - I mean we have to > list all the file types used as source files and those files types do change > - their set is getting extended - IOW still manual testing/fixing scripts > will be needed I think. > > I haven't time to automate that work - we can make it automated here all > together by writing batches and/or simple C# utitlity controlling such > automated update - whatever would be less time consuming. > > It might happen I'm missing more straightforward way of doing such > synchronbization between your server and CodePlex assumed your server is a > master but CodePlex files have difference version numbers controlled by > CodePlex server. > > Thank you. > > -- > Shamil > >