svn - Committing broken code to the repository for the purpose of backing it up -


I was just talking to another developer (more senior than me) and trying to explain it That we should implement continuous integration through cruise control. He told me that this will not work because he changes the code that does not compile it for repositories at all times for the purposes of support. And that indicates automatic failures only will be noise.

Making garbage in repo seems bad for me but I had a loss of words and did not know what to say. What is optional? What is the best practice to support your code on another machine without adding a group of redundant amendments?

BTW, our version control system is SVN and it will probably not change any time soon.

To be ready to develop and test in branches and hopes that branches work in the main line Have to do. Constant integration for new modification to build and validate depends on the server main line (Says Trunk in SVN).


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -