Hi,
How to run ready api composite project in gitlab with license.
I am getting the following error:
No valid SoapUI license exists.
Please enter absolute path of the license file (.zip or .key):
[INFO] ReadyAPI 2.6.0 shutting down
[ERROR] java.util.NoSuchElementException: No line found
Solved! Go to Solution.
As far as I understand you can not share fixed licenses, they have to be deactivated on the old machine before they can be installed and activated on a new one, if you are having problems deactivating contact SmartBear support.
We had to purchase an additional fixed license for our Jenkins CI server.
As an alternative to the fixed licences, you can get floating licenses that can be shared, though I have no experience of these.
This means ReadyAPI is being ran on either a machine that doesn't have a license, or as a user who doesn't have a license on that machine. ReadyAPI is licensed, as far as I am aware, per user per machine. So if you log onto a machine, and insteall ready api as "SIRIS" user, but Gitlab runs ReadyAPI as "GITLAB" user, that user does not have a license.
depends on your machine which install ReadyAPI with license. If you run on Master, your ReadyAPI should install with license, If you run on Slave, your ReadyAPI should install with licese on Slave.
Copy command line to run on local and then debug in GitLab.
BR,
/Aaron
Thanks for your help, Community,
@Siris, did the suggestions posted here help you?
Thanks for the reply. Now I need to find out on how to run the Ready API project from CI/CD server(GitLab). Can the license be shared?
Hi,
I tried that also but I got an error as "ERROR: The license is invalid: The license can not be activated as the number of allowed copies has been exceeded"
Not sure on how to install license on gitlab server
As far as I understand you can not share fixed licenses, they have to be deactivated on the old machine before they can be installed and activated on a new one, if you are having problems deactivating contact SmartBear support.
We had to purchase an additional fixed license for our Jenkins CI server.
As an alternative to the fixed licences, you can get floating licenses that can be shared, though I have no experience of these.
What @Radford said. Licenses cannot be shared if they are fixed licenses. We had to use one of our spare licenses on our Jenkins server to be able to run ReadyAPI there for testing automation.
User | Count |
---|---|
3 | |
2 | |
1 | |
1 | |
1 |
Subject | Author | Latest Post |
---|---|---|