Our current Jenkins process is pretty typical (I assume).  Namely, we have a build definition associated with a Jenkins build engine.  Jenkins does polling via the plugin to know when to fire the build at which time it loads the workspace defined in the build definition and then runs the build command specified in the Jenkins job.  That works well enough, we've been using it for years.

Now we are looking at using a Jenkins pipeline in order to simplify the master build script and use the cleaner semantics of a pipeline.  Configuring the pipeline in the script block in the Jenkins job works but my question is can using a Jenkinsfile pull from SCM work at all?  It just seems out of kilter conceptually in that a stream holds multiple components which for most Jenkins users are their own single repositories.  In an RTC workspace situation Jenkins wouldn't know which component to look in for the Jenkinsfile - unless they all had Jenkinsfiles (which is maybe the expectation).

Could someone share their experience using Jenkins, Pipeline and RTC?