What version of DevTest are you using? Certain enhancements have been made in regards to our Jenkins plugin since 10.3.
Are you currently creating the MAR file manually and then attempting to deploy the virtual service through the MAR file? And while deploying it through Jenkins, you want to pass in the configuration file as a parameter so that the virtual service gets deployed to that specific environment?
If this is the case, one suggestion is to create three MAR files one with each configuration (manually or through our MakeMar.exe command line utility) and then in your Jenkins pipeline select the appropriate MAR file, out of the three you created, based on the configuration parameter.
You could also create a MAR Info file, which can be used to create the MAR file. The MAR Info file contains all the information, such as the configuration to be used, for creating the MAR file. Here is an example of the content of a MAR file:
<?xml version="1.0" ?>
<MarInfo>
<name>MyVirtualServiceName</name>
<type>VIRTUAL_SERVICE</type>
<projectRoot>MySVProjectName</projectRoot>
<optimized>true</optimized>
<deployInfo>
<PrimaryAsset>VirtualServices/MyVirtualServiceName.vsm</PrimaryAsset>
<Configuration>Configs/project.config</Configuration>
<ConcurrentCapacity>1</ConcurrentCapacity>
<ThinkTimePercent>100</ThinkTimePercent>
<AutoRestart>true</AutoRestart>
<StartOnDeploy>true</StartOnDeploy>
</deployInfo>
</MarInfo>
The above bolded part is where you can change the configuration file to be included in the MAR. So during your Jenkins pipeline execution, you could potentially make a copy of this baseline MAR Info file and change that one line and replace it with a different config file. Then build your MAR file dynamically, using this MAR Info file and DevTest_HOME/bin/MakeMar.exe. Finally deploy the virtual service using the newly build MAR file.