This is a growing space and we will continue improving support throughout the year. As mentioned, we do have prpcUtils which is ANT-based and can be called from a custom Jenkins job, or other CI tool.
You may also wish to consider the ProductMigration tool as an alternative to prpcUtils to automate your RAP deployments. This tool can operate without needing a third system to orchestrate the process, as well, but it does require direct communication between the source system where the RAP is defined and the target system where it will be imported to.
In 7.2, we introduced prpcServiceUtils which makes the scenario a little more flexible than prpcUtils as it is a REST-service-based and doesn't require database communication.
In 7.2.1, we are going to be releasing REST services to execute test groups and get the results back in xUnit format, so these can be easily called from a CI tool.
Lastly, we will have some exciting things to show at PegaWorld 2016. We will talk a lot more about supporting Continuous Integration and Deployment pipelines and tools during the DevOps bootcamp on Wednesday and at the DevOps booth. Please stay on the lookout for that!
Is it required for the Jenkins also to be deployed and installed in the same network / machine as the source server for Pega? can Jenkins installed in a different container be used to invoke the PrpcUtils / PrpcServiceUtils to export jar from source and deploy to target?
Since with 7.2 the prpcServiceUtils make use of REST APIs and urls for source and target, I would assume that the same can be called from a Jenkins server or other CI servers hosted on a different machine.
You can write Shell script/Ant script which can be used to export rules from the sorce environment and import the same into the target environment. These shell/ant scripts can be invoked from Jenkins to enable your deployment and infact your deployment can be automated using this.