title: CCNet vs Jenkins - one point configuration for multiple branches
body: <p>I recently heard a lot about jenkins, it's cool UI, easy to set up, so many plugins etc.. Currently I am using CCNet for CI. I thought of migrating to Jenkins looking at its cool features.</p>
  
  <p>Soon i realized Jenkins lacks the most important feature - one point configuration - Define all the common configurations at one place and reuse them for multiple projects. Later I found there are couple of options available in Jenkins like copy from existing project or use Jenkins web API.</p>
  
  <p>Problem with "Copy From existing project" is if i make any change in this project it won't be automatically reflected in all the projects copied from this.</p>
  
  <p>There are environment variables but these are like global variables. </p>
  
  <p>CCNet on contrary has very cool feature of "<a href="http://www.cruisecontrolnet.org/projects/ccnet/wiki/Configuration%20Preprocessor" rel="nofollow">Configuration Preprocessor</a>" which is the core strength of ccnet i believe.</p>
  
  <p>My conclusion is Jenkins is easy to setup and useful in case you have few projects.It becomes very difficult to maintain Jenkins as the number of projects increases.
  CCNet is difficult to set up for the first time but once setup it requires minimal effort for any one to add a new project.</p>
  
  <p>So my final thought was I won't be migrating to Jenkins.</p>
  
  <p>Please share your thoughts on this and if people have faces similar issues when migrating? Also i would like to know if missed anything important in my analysis.</p>