File status control
Hi, I am part of the quality management at my company and we use SVN as our source code repository. I would like to know if is there a way in which I can control the "STATUS" of a file (and its status-changes) ? Example: lets say that we have the following statuses: UnderDevelopment, Tested, Approved and Declined Only SOME of the "Change of status" are allowed. For instance, a file cannot be set as "Approved" if it has not been "Tested" before. I would like to know what is used so far to accomplish this task. Thanks a lot
RE: File status control
Guten Tag Thorsten! that's what I've imagined. We actually have to use SVN as a sort of configure management system. I am currently writing a pre-commit hook so we can control it without using the "svn:properties" (we've decided to add a flag on the commit messages with the current file statuses. It doesn't look much elegant but this was the only way we've managed to have it "user-friendly"//acceptable for the developers. It seems weird though that subversion has not a native way of doing so, people from the "quality departments" love this sort of functionality. Dankeschön From: Thorsten Schöning [tschoen...@am-soft.de] Sent: 27 November 2012 14:05 To: users@subversion.apache.org Subject: Re: File status control Guten Tag armando.perico.n...@usi.ch, am Dienstag, 27. November 2012 um 13:47 schrieben Sie: > I would like to know what is used so far to accomplish this task. Subversion provides versioned properties which could be used but from my experience most projects seem to not think in cases of status for files, but more in logic way of patches, branches etc. Patches of specific versions can often be reviewd during special tools like bug trackers as Bugzilla or special review web applications were many devs can look at specific branches. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
RE: File status control
Hi Andy, you are probably right if we think only about code and software projects; however, the needs for these features here are to control "documentation projects" i.e.: to handle documents for ISOs and IECs standard implementation (we pretty much handle .doc files - no need to handle line diffs and merges for instance). Note: An important requirement here is that the path of the document shall never change once it has been defined and published internally. Some uses cases: - Only create a "release" versions of the documentation when all the documents are with the "approved" status. - Only specific author can make revisions - A document cannot be "approved" if it has not been "reviewed" and so on... I am not comfortable yetwith the solution we're planning to use in order to solve this, however, it seems to be the solution with less "side-effect" to the users (once SVN is already used as a repository system for the documents). I am still trying to put the ideas together to come up with a good solution. I am open to suggestions... From: Andy Levy [andy.l...@gmail.com] Sent: 27 November 2012 15:24 To: Perico Neto Armando Cc: users@subversion.apache.org Subject: Re: File status control On Tue, Nov 27, 2012 at 8:44 AM, armando.perico.n...@usi.ch<mailto:armando.perico.n...@usi.ch> mailto:armando.perico.n...@usi.ch>> wrote: Guten Tag Thorsten! that's what I've imagined. We actually have to use SVN as a sort of configure management system. I am currently writing a pre-commit hook so we can control it without using the "svn:properties" (we've decided to add a flag on the commit messages with the current file statuses. It doesn't look much elegant but this was the only way we've managed to have it "user-friendly"//acceptable for the developers. It seems weird though that subversion has not a native way of doing so, people from the "quality departments" love this sort of functionality. I never consider "file" statuses for the items in my source code repository - only the status of the entire project, via my tags & branches. Releasing individual files to an environment (at least for software my team and I have built) would just lead to large amounts of confusion, and broken releases.
Pre-commit fails when executing 'svn ls'
Hi, I want to write a pre-commit hook which make some checks on the repository using "svn" commands. i.e.: svn ls... however, svn ls is failing to connect to localhost. on my pre-commit file I have: --- # I don't need the $REPOS value since this is just a test svn ls http://localhost/svn/repo/ --username=X --password=Y --non-interactive exit 0 --- The script works fine when I run it "manually" (even when I run it with the "apache" user) example: sudo -u apache env /var/www/svn/hooks/precommit (works ok) su -s /bin/sh apache -c "/var/www/svn/hooks/precommit" (works ok) however, when I run it with any "svn client" I get the following: svn: OPTIONS of 'http://localhost/svn/repo/test.txt": could not connect to server (http://localhost) I can't understand why it is failing. Would anybody have a suggestion ? Thanks
RE: Pre-commit fails when executing 'svn ls'
Yes, it was the SELinux messing with my life again, it works now! (it actually saved my afternoon, I was debugging it for a loog time already) Since this is a test//prototype environment, I've turned the SELinux it off completely (is ok for me). However, it would be nice to know how to properly allow it with the SELinux ON). * I will look in to it as soon as I can and post here when I have something. (if someone has already the configurations pls put them here too) Thanks a lot for the help! From: Thorsten Schöning [tschoen...@am-soft.de] Sent: 28 November 2012 16:57 To: users@subversion.apache.org Subject: Re: Pre-commit fails when executing 'svn ls' Guten Tag armando.perico.n...@usi.ch, am Mittwoch, 28. November 2012 um 16:43 schrieben Sie: > svn: OPTIONS of 'http://localhost/svn/repo/test.txt": could not > connect to server (http://localhost) SELInux or AppArmor may prevent communication as both work on binaries I think, not on users, therefore your test would succeed. A lot of people having issues like that if they try to send mails using httpd: http://stackoverflow.com/questions/1462941/php-mail-works-from-command-line-but-not-apache/1467900#1467900 Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
