Guten Tag Charlie Davis,
am Dienstag, 31. Mai 2011 um 19:59 schrieben Sie:
> The problem I've come across is that SVN COPY doesn't work if the file
> exists... so... I made my script do a SVN delete, then a SVN COPY, and
> this creates a commit... and we get an infinite loop.
If your script is triggered through keywords in a log message, why not
just omit those keywords in your automatically generated commit in the
script? They aren't useful anyway for QA, it's only a tool for your
developers to get they're commit into the release. Without those
keywords in your log message I don't see where the infinite loop could
happen. Just a svn copy without the delete would have triggered a
commit and a infinite loop, too. Everything creates a commit.
Besides that I don't think it's a good idea to delete and copy all the
way, because it makes debugging in case of an error harder than
necessary. If I change a file, commit it, delete another one and copy
the former changed file to the deleted, I don't get a diff of the real
changes but only the contents of the copied file. If QA finds an
error, you have to go to the log, look for the versions the copied one
differs in the former copied version and can't just work with a diff
of the changes to the file version QA got merged. What happens if a
developer made more than one commit to a file during his work and only
the last log message tells your script to copy the file. QA gets all
content because of the copy, but what does the log message tells QA
about the changes made?
Therefore I would prefer proper proper merging by the developer,
because you get a useful diff and log message in the changed file for
QA.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail: tschoening_at_am-soft.de
Web: http://www.am-soft.de
AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
Received on 2011-06-01 09:01:19 CEST