title: Understanding what differentiates jenkins and django-jenkins
body: <p>My question is rather subjective, moderators please do not close it, for I want to know the views of experienced nerds. </p>
  
  <p>I am new to deployment arena, and was doing some RTFM on <a href="http://jenkins-ci.org/">jenkins</a>, coming from python/django background I searched github to find <a href="https://github.com/kmmbvnr/django-jenkins">django-jenkins</a>. </p>
  
  <p>The whole idea of CI is to have a continuous build process, so that you can revert to your last stage if build fails. </p>
  
  <p>As far as I could make out, jenkins runs on a server, which runs test and deploys if all the tests pass, when code is pushed to github or some other repo. It might talk to the repo by means of polling or cron jobs. </p>
  
  <p>Whereas when I looked at django-jenkins in the documentation it is mentioned </p>
  
  <pre><code>./manage.py jenkins
  </code></pre>
  
  <p>This means, we can add commands to settings file, test things locally and then deploy. (correct me if I am wrong)</p>
  
  <p>So what differentiates it? Does django-jenkins remove any need of an additional server that uses jenkins for CI?</p>
  
  <p>Please let me know, and clear me where I am wrong. </p>