Thank you to everyone who joined this webcast on August 30, 2018 which featured a presentation and demo on the new CA Service Virtualization Jenkins Plugin. A big thanks to Petr Vlasek and Alan_Baptista_DevOps-SV for presenting this topic to the community!
Below are all the relevant webcast materials:
Hi, one of the Q&A items we have got during the webcast and where we owe the clear answer was the following one:
There are multiple virtual services with the same names coming from different projects - which one will be started by the CA SV Jenkins plugin?
As some of you already pointed out during webcast Q&A session - once virtual service is deployed to VSE, it is project agnostic. In other words, you cannot deploy more virtual services with the same name to the same VSE. So there cannot be any such ambiguous case about to which virtual service with the same name to start.