• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 15 replies
  • Subscribers 7 subscribers
  • Views 8577 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Setting up Jenkins to run automated tests against expression rules

steveb

I'm trying to set up a Jenkins job to run automated tests against our expression rules.

I've followed the steps outlined on the help page (avivadev.appiancloud.com/.../Running_Automated_Tests_on_Expression_Rules_with_Jenkins.html

However when the Jenkins build job runs it fails with the following message ...

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'SystemTest'.
> Could not resolve all dependencies for configuration ':classpath'.
> Could not resolve org.codehaus.groovy.modules.http-builder:http-builder:0.7.2.
Required by:
:SystemTest:unspecified
> Could not resolve org.codehaus.groovy.modules.http-builder:http-builder:0.7.2.
> Could not get resource 'jcenter.bintray.com/.../http-builder-0.7.2.pom'.
> Could not G...

OriginalPostID-223153

OriginalPostID-223153

  Discussion posts and replies are publicly visible

Parents
  • 0
    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.
Reply
  • 0
    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.
Children
No Data

© 2024 Appian. All rights reserved.