We are using SVN as the source control for our Pega Robotics projects and Jenkins as our CI tool. We are trying to automate the Pega Robotics solution file (.ossln) in Jenkins. Below are the things we tried,

Using MSBuild:

1. Renamed the .ossln file to sln file and used the msbuild command to perform the build
2. We are able to create the _Debug.OpenSpan, _Debug.manifest and the _Release.OpenSpan, _Release.manifest files. However, we are unable to create the environment specific deployment packages that are created based on the solution Configuration settings (i.e. _QA.OpenSpan, _QA.manifest and _Production.OpenSpan, _Production.manifest)

Upon further investigation, we found that the msbuild command invokes the C:\Program Files (x86)\OpenSpan\OpenSpan Studio for Microsoft Visual Studio 2015\OSD.exe command which takes a /configuration parameter, which can be set to “Production” or “QA” to get the desired deployment files based on the 

What we need:

1. Is there a way to pass the /configuration parameter directly from MSbuild so that the OSD command can read it and create the corresponding output files?
2. If we directly invoke the OSD.exe command, it requires a /References parameter, which expects individual dlls to be included in the command line. Is there a way it can read the references directly from the solution file?
3. If all of the above is possible, then is there a way to pass the deployment version to this process, so the *manifest file has the desired version?

Our current configuration:

Pega Robotics Studion 8.0.2061

We do not have Robot Manager