title: pass parameter to pipeline script
body: <p>I'm trying to switch from using a freestyle Jenkins build to a pipeline project. </p>
  
  <p>I like many things about it, but I wish that I could use the multibranch pipeline as that matches our company a bit better, but at present that is a not an option. </p>
  
  <p>What we do currently is create a new build job with the name of <code>&lt;project name&gt; - &lt;environment&gt;</code>. </p>
  
  <p>So I need to keep that going for now. I have a basic outline of a script that I can either copy and paste into the box or even better is to use the jenkins file from scm. </p>
  
  <p>I like this one the most and that is what I'm currently using on my local Jenkins. </p>
  
  <p>If I hard code the solution file and the environment I want in my script in scm it builds fine. </p>
  
  <p>I don't like that option because that means I'd have to have lots of scripts with similar names just changing the branch. If I add build parameters with the solution name and environment I can easily make the script handle those as well, however what I don't like is that when I click build button it confirms that those are the parameters I want to use. </p>
  
  <p>So is there a way that I can hardcode/get a plugin that lets me add those parameters as constants or environment variables or whatever so it is just part of the job?</p>
  
  <h3>EDIT</h3>
  
  <p>As an update to show what I tried yesterday and got to work for our needs is this. First was that I installed <a href="https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Multibranch+Defaults+Plugin" rel="nofollow noreferrer" title="multibranch defaults plugin">multibranch defaults plugin</a> and followed the steps outline on their <a href="https://github.com/jenkinsci/pipeline-multibranch-defaults-plugin#configuration-steps" rel="nofollow noreferrer">github page</a>. With that installed and configured I added a new multibranch project, pointed it to my git repository. It now found 2 branches (as expected) and used the default config file. So far this seems like it will work for about 90% of our cases. The only problem I can see is if some people had custom steps in their existing freestyle project. But for now those can always just stay a freestyle project.</p>