Saving time in SVN connections after commit?

Question

At my place of work, we started introducing the right SVN hooks, the "right" values, "doing a lot of policy checks." Our policy currently consists of Perl :: Critic with Perl :: Tidy validation. However, especially the latter takes a lot of time to commit with several or many files, and SVN did not return until a post-commit hook was made.

Is there any way to save time on the hook after committing without sacrificing policy checks?

Answer 1

If you only want a report (for example, a list of errors), you can use Continuous Intergation to perform some actions after the transaction. These systems allow you to perform any action after making changes to your version control system. Here is an example script:

• Someone commits SVN repository
• After a while, CC detects this change and runs the script:
  • Get the latest version from SVN
  • Run checks like Perl :: Critic and Perl :: Tidy
• If any verification was not performed,
  • Create a detailed error report (which is accessible from the Internet)
  • Email if necessary

There are many good systems of continuous interaction. I like Hudson .

Answer 2

, . , , . , trunk - . , , . , , .

Answer 3

, , "", , .

, , . ( : . .)