Ready API. Shows exception on Jenkins com.smartbear.ready.license.exception.InvalidLicenseException

[vpachpute1]

Hi

I have Ready API 1.9.0 License. It's working fine on my local maching and using maven plug-in on my local machine.

But when I run it on Jenkins server using pom.xm, it shows exception as "com.smartbear.ready.license.exception.InvalidLicenseException

As there is no license on Jenkins server

Is there is any other way to do so. Actually I am using one important feature of Ready API i.e. Composite Project. So I needed ReadyAPI.

Can anyone please suggest any solution. Thanks in advance.

Attached my pom.xml file for reference.

[VLapidus]

Hello,

Please refer to the article. Does it help?

[vpachpute1]

Hi

Thanks for your reply.

From Article: "Whether you are running Jenkins independently as a service or on your application server, you need to ensure it is running with the same user account you activated the SoapUI NG license with."

Actually in my case, there License in on my local Ubuntu machine.

And jenkins is independent environment which is different server at different location.

So can you please confirm that weather this solution works in this environment ?

regards

Vishal Pachpute

[VLapidus]

Hello Vishal,

No. You need to run Jenkins under the account where the license is activated. Alternatively, you can deactivate the license on a local Ubuntu computer and activate on a computer with Jenkins.

[vpachpute1]

Hello

Just some questions. can you please clear that

1. In the article, there are steps to configure jenkins service with user on Windows. So is there any article for same thing on Ubuntu ?

2. While activating the license, I just provided Email Address and my basic info and given path of the license key file.

So there is step "enter the user account name and password you activated the SoapUI NG license with."

Which user account name and password should be provided. ?

3. On my Jenkins server, there is docker image. So is this needs to activate license each time when image is created and deactivate license when image is destroyed ?

Please clear if I am wrong in some things.

Regards

Vishal Pachpute

[vpachpute1]

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

[VLapidus]

Hello Vishal,

1. Unfortunately, no.

2. It should be your computer account name and password.

3. A license is placed to the <User>\.soapui folder after activation. If the folder is recreated then yes.

[vpachpute1]

Hi

Thanks for your reply.

So here you want to suggest

Separate license will be required. One for my local machine and one for jenkins server which is at different location ?

Regards

Vishal

[andym]

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.

[VLapidus]

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.