Forum Discussion

tamnor's avatar
tamnor
Occasional Contributor
10 years ago

Not able to run ReadyAPI tests from Jenkins due to error : No valid SoapUI NG license exists.

Hi,

I am trying to run some Ready API Maven tests from Jenkins but I am getting the below errors in the Jenkins console log.

    No valid SoapUI NG license exists.
    Please enter absolute path of the license file (.zip or .key):

 

I have searched this error online and one of the suggestions for a common cause was "you are not running Jenkins with the same user account you activated the SoapUI NG license with. " (http://readyapi.smartbear.com/about/licenses/troubleshooting/jenkins)

 

I am not able to check what user I am running Jenkins with as I don't have admin privileges, but I assume it would have to be my user as I installed it.

 

I am running all this all on my local machine so Jenkins is installed on the same laptop as Ready API which has an active license. (The plan is to have this set up on a VM soon but am just doing it all from my local machine as initial proof of concept)

So I'm not sure if that cause applies for this scenario. The licence was initially activated by our helpdesk on my old machine, however when I got a new machine. I am pretty sure I activated the licence offline myself. Is there anyway in Ready API to tell which user activated the licence?

 

Could someone please give me some advice about how I could go about fixing this issue.

 

Just in case it is relevant ..

I have some SoapUI (open source) / Maven project which I am able to run from Jenkins without issue.
I can run the Ready API / Maven project from Maven without any issue.

 

Below is Jenkins console output ..

 

16:38:20,724 INFO  [PluginManager] 0 plugins loaded in 0 ms
16:38:20,724 INFO  [DefaultSoapUICore] All plugins loaded
No valid SoapUI NG license exists.
Please enter absolute path of the license file (.zip or .key):
[ERROR] java.util.NoSuchElementException: No line found[JENKINS] Recording test results
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 01:22 min
[INFO] Finished at: 2016-11-01T16:38:20+00:00
[INFO] Final Memory: 41M/470M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.smartbear:ready-api-maven-plugin:1.9.0:test (default) on project my-myreadyapiapp: Ready! API Test(s) failed: Ready! API Test(s) failed:[ERROR] No line found[ERROR] -> [Help 1][ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.[JENKINS] Archiving C:\MavenProjects\my-myreadyapiapp\pom.xml to com.myreadyapimvnproj.app/my-myreadyapiapp/1.0-SNAPSHOT/my-myreadyapiapp-1.0-SNAPSHOT.pom
[ERROR] Re-run Maven using the -X switch to enable full debug logging.[ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles:[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
channel stopped
Finished: FAILURE

"

1 Reply

  • Hi Tamnor,

     

     

    I see that you've contacted our Support Team regarding this issue. Let me quote their answer here as it can be helpful for other community members:

    The Jenkins service is running under the Local System account ( http://screencast.com/t/MbBAiFy4cav ) rather than the user account, you installed it with. In this case, the licensing issue is expected. So, for fixing the issue, the steps from this article should be performed: http://readyapi.smartbear.com/about/licenses/troubleshooting/jenkins

    If you don't have permissions for editing the Jenkins service settings, please ask your IT team to do this.