Setting up Jenkins to run automated tests against expression rules

RE: Setting up Jenkins to run automated tests against expression rules

PriyeshPSingh — Thu, 17 Jun 2021 10:34:53 GMT

me too

RE: Setting up Jenkins to run automated tests against expression rules

toyerm — Fri, 09 Jun 2017 09:02:21 GMT

Hi guys, has anyone managed to get this jenkins job running? I am still battling with the error" > Could not resolve org.codehaus.groovy.modules.http-builder:http-builder:0.7.2."

RE: Setting up Jenkins to run automated tests against expression rules

sneham — Wed, 24 Aug 2016 17:45:16 GMT

Seems the gradle task is not able to make the post request, you can try checking the URL that is formed at run time in the build.gradle, and making the post request using CURL command to check if the web-api is working fine.

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Wed, 24 Aug 2016 17:29:51 GMT

Unfortunately neither suggestion worked. Adding the systemProp.xxxx statements, with the appropriate values, to either end of the properties file makes no difference. I get the response

:runApplicationTest
Start System Test
:runApplicationTest FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\\Program Files (x86)\\Jenkins\\workspace\\ApplicationTest\\build.gradle' line: 47

* What went wrong:
Execution failed for task ':runApplicationTest'.
> This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server

I assume my company has put in place additional security which is blocking the request.

I did manage to get the file(s) from codehaus using the original build script, but only by downloading and installing Gradle and running the script directly from the CMD> line.

RE: Setting up Jenkins to run automated tests against expression rules

sneham — Wed, 24 Aug 2016 12:59:47 GMT

Yes, these proxy details are added to the "gradle.properties" file, this is the same property files as mentioned in the Appian help document.

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Wed, 24 Aug 2016 12:31:31 GMT

Is the Gradle properties file you refer to the same one the Appian help asks you to create with the user id and base64 password in ?

Looking at Gradle's help it suggests putting the following in the "properties file" (is this the same one as above ?)

systemProp.https.proxyHost=www.somehost.org #
systemProp.https.proxyPort=8080 #
systemProp.https.proxyUser=userid #
systemProp.https.proxyPassword=password #
systemProp.http.nonProxyHosts=*.nonproxyrepos.com|localhost

With any text suffixed with # (eg www.somehost.org) being replaced by my company's details

RE: Setting up Jenkins to run automated tests against expression rules

sneham — Tue, 23 Aug 2016 10:50:45 GMT

Hi Steve,

I recently configured jenkins to run test case for rules on my environment, some quick suggestions that may help resolve your issues

a: Check if your network is behind proxy, if yes, then you need to add proxy authentication details(for both http and https) in gradle.prperties file(Please refer the documentation of gradle for the same)

b: If doing step does not resolve the issue you can use an alternative maven url for the http-builder:0.7.2 dependency
following is the buildscript snippet for build.gradle that worked for me

buildscript {
repositories {
mavenCentral()
maven {
url "repo.spring.io/.../"
}
}
dependencies {
classpath 'org.codehaus.groovy.modules.http-builder:http-builder:0.7.2'
}
}

RE: Setting up Jenkins to run automated tests against expression rules

Tom Ryan — Tue, 09 Aug 2016 10:03:16 GMT

I'm not a Jenkins expert so I couldn't say. Feel free to re-post your question to see if any other practitioners have other suggestions.

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Mon, 08 Aug 2016 14:33:59 GMT

Hi Tom, unfortunately no, hence my question as to whether there was an alternative way of approaching this.

RE: Setting up Jenkins to run automated tests against expression rules

Tom Ryan — Mon, 08 Aug 2016 04:21:28 GMT

Hi Steve, in an earlier post you mentioned that there was a permissions issue that was apparently preventing the dependencies from being downloaded. Was this already resolved?

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Fri, 05 Aug 2016 23:30:00 GMT

Hi Tom

Are there any other ways of constructing the Gradle build file that doesn't reference the org.codehaus.groovy.modules.http-builder:http-builder:0.7.2 as we still cannot get round the problem I've mentioned above.

Alternatively are the any other ways of integrating with Jenkins that doesn't involve Gradle ?

Thanks
Steve

RE: Setting up Jenkins to run automated tests against expression rules

Tom Ryan — Fri, 15 Jul 2016 04:00:42 GMT

Our only suggestions for Jenkins setup/configuration are those mentioned in the docs:

forum.appian.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html

However, depending on your environment, it may be that additional or different steps are required.

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Thu, 14 Jul 2016 20:57:08 GMT

Hi Tom
Thanks for the suggestion. Further investigation suggests it is a permissions issue with the parent folder the Jenkins workspace folder is in. I copied the build file into a different folder and ran Gradle, which I downloaded separately, against it. Whilst the script failed it managed to process the steps that retrieved the data from the url. This was sufficient for me to then successfully run the project in Jenkins.

I'm not sure if this is what Appian expect people to do, but at the moment it works although I will shortly be using a different Jenkins server so may be back.

RE: Setting up Jenkins to run automated tests against expression rules

Tom Ryan — Wed, 13 Jul 2016 03:39:46 GMT

Based on the error it seems there is an issue downloading dependencies. The error suggests that this could be temporary, so it is worth trying again and seeing if the same error is reproducible. If it is, ensure that the host is able to resolve the URLs mentioned there. You could also try running with the --stacktrace option to get more information as to what went wrong.

RE: Setting up Jenkins to run automated tests against expression rules

steveb — Tue, 12 Jul 2016 12:20:00 GMT

...ET 'jcenter.bintray.com/.../http-builder-0.7.2.pom'.
> This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Any suggestions as to how to resolve this ?

Thanks
Steve