Your descriptions of what pjam did sounded so wonderously buzz-wordy - thank you, I will improve documentation, (:

Also I wouldn't call svn log && svn up "scm integration" :) May be term I used not that understandable. But what I meant - pjam is intended as tool one can use in processes of continues integration, one of a part of it is a continues builds upon changes in a sources code, commonly stored in SCM system. Currently the implementation is quite primitive, but it's just a prototype, one day I may want to bring it to Jenkins or some others CI platform, but try to think about the idea behind pjam, not the current implementation.

giant if/else trees don't lend to extension very well or collaboration ... they're not plugins who said it should ? pjam is not a plugin, it's tool with command line api, plus web server api (limited api to pjam client) + some concept of directory layouts and business logic; It's not a library; It's not intended to be reused in this way; It's just intended to be used directly, as said in docs. And once again, I saw so many comments concerning code style, I'd agree with such a criticism in context of ideal code, but for end user it just works, why one should care about source code, while it works?; One day I will refactor that all, and I will, once again it *just work for me*, and it may work for others;