title: Jenkins Declarative Pipeline without Jenkins file in the repository
body: <p>I am trying to upgrade my current regression infrastructure to use <a href="https://wiki.jenkins.io/display/JENKINS/Pipeline+Plugin" rel="nofollow noreferrer">pipeline plugin</a> and I realize there are two methods: <code>scripted pipeline</code> and <code>declarative pipeline</code>. Going through multiple articles, I realize that <code>declarative pipeline</code> is more future proof and more powerful, hence I am inclined to use this. But there seems to be following restrictions which I don't want to have in my setup:</p>
  
  <ol>
  <li><p>The <code>jenkinsfile</code> needs to be in the repository. I don't want to keep my <code>jenkinsfile</code> in the code repository. </p></li>
  <li><p>Since the <code>jenkinsfile</code> needs to be in SCM. Does it mean I cannot test any modification in the file until I check that in to the repository. </p></li>
  </ol>
  
  <p>Any details on the above will be very helpful.  </p>