Hi
description about Jenkins Server:
The Jenkins server is running Linux, and is headless, and does not run any X server software, and user interaction during the building of docker images and execution of docker containers is of course not possible.
Jenkins server runs the application that is being tested, as well as the SoapUI test client, within docker containers. These docker containers are created at the start of the test, and stopped+destroyed at the end of the test. The docker images from which the docker containers are started are themselves created on a frequent (but irregular) basis. There is only one Jenkins master server, but of course the actual execution of the containers is offloaded to one of a set of currently available slave nodes.
We would like to use features included within the professional version of SoapUI, and so ensure this is correctly licensed, but don't understand the mechanics of how this can be achieved. Can you please describe how we should do this? If this isn't possible then the only other option would be the use of the unrestricted free version of SoapUI.
Regards
Vishal Pachpute
Regarding our use of docker, here are some specific follow-up questions which will probably be helpful for us (and others) to evaluate whether it's feasible to use the licensed version within docker containers:
1a: Have you internally tested SoapUI within docker containers, including licensing, and verified that no issues are introduced with this approach?
1b: Do you explicitly support, or explicitly do not support, it?
1c: Do you have any documentation on this? (NB: due to the popularity of docker used within test environments, such documentation would probably be useful for many people)
2. Docker containers typically run with a different IP address every time. Is this likely to cause any licensing issues?
3. Test client docker images can be newly recreated on a frequent basis. Would such frequent licence reactivations cause any problems (e.g. raise any fraud alerts)?
4. When (re)creating the test client docker image (which would likely involve a step which activates the licence), there is no capability for us to run a container from the previous docker image in order to deactivate the license before reactivation. Is this likely to cause any issues?
Thanks.
Hello,
Vishal, yes, you are right.
>>>1a: Have you internally tested SoapUI within docker containers, including licensing, and verified that no issues are introduced with this approach<<<
No, docking containers were not tested.
>>>1b: Do you explicitly support, or explicitly do not support, it<<<
We cannot say anything about is as they were not tested.
>>>1c: Do you have any documentation on this<<<
No.
>>>2. Docker containers typically run with a different IP address every time. Is this likely to cause any licensing issues<<<
It should not cause issues but sometimes a license may be corrupted.
>>>3. Test client docker images can be newly recreated on a frequent basis. Would such frequent licence reactivations cause any problems<<<
Yes, the number of deactivations is limited.
>>>Is this likely to cause any issues<<<
Yes, you will lose a license if you do not deactivate it before recreation and will have to contact Customer Care.
