Hi Tom, Looks like the value of webserverHome is empty. Can you try passing a value in the ant call. Something like ant -DwebserverHome=<path_to_glassfish> config.vi The ts.jte you had pointed also has empty default value. You can run ant target in debug mode to analyze further. Hope it helps. Regards Anand. From: Tom Jenkinson <tom.jenkinson@xxxxxxxxxx>
Sent: Thursday, July 4, 2019 2:03 PM
To: EE4J PMC Discussions <ee4j-pmc@xxxxxxxxxxx>; jakartaee-tck-dev@xxxxxxxxxxx
Subject: Re: [ee4j-pmc] Fwd: [jakartaee-tck-dev] TCK information Adding in the JakartaEE TCK dev mailing list for my request for help below about running the TCK for the JTA. I am producing the Jakarta Transactions TCK jobs but running into a problem with actually executing the 3rd job (the main one that runs the TCK). I think the pipeline is trying to set up a server and is failing here: I wonder if anyone else is in the same position and had some suggestions. The source script is here: The last useful output from my job is: config.vi:
[echo] ts.home = /home/jenkins/workspace/TCK_run_pipeline/jtatck/bin/xml/../..
[echo] In a bundle
[echo] The deliverable currently in use is /home/jenkins/workspace/TCK_run_pipeline/jtatck/bin/xml/../../bin.
-delete.tck.ext.jars:
BUILD FAILED
/home/jenkins/workspace/TCK_run_pipeline/jtatck/bin/build.xml:81: The following error occurred while executing this line:
/home/jenkins/workspace/TCK_run_pipeline/jtatck/bin/build.xml:88: Directory /domains/domain1/lib/ext creation was not successful for an unknown reason Thanks for any suggestions! FYI — Dmitry
Subject: [jakartaee-tck-dev] TCK information Date: 24 June 2019 at 23:50:34 CEST Dear Jakartees,
With the upcoming Jakarta EE 8 release, and updated APIs to be released for it, as most of you likely have heard, the TCK for each API is to be run. As the main goal is to check the compatibility of the API for this release, we have provided a few notes about how to do it:
- We have summed up some information about how the TCK can be built (or grabbed pre-built), configured, and run [1].
- This is assumed to be run against a Glassfish with the latest API integrated (replacing the original API in the Glassfish).
- We have created a recording of a presentation of the Jenkins jobs that manage all that [2].
- We have created 3 Jenkins files for pipeline job (as an example for JSON-B TCK) to a) properly set the ts.jte configuration file, b) to grab the API artifact built by a Jenkins build job and integrate it to a Glassfish and c) to grab the pre-built TCK bundle from Eclipse Download, grab the configured ts.jte file, grab the Glassfish with new API integrated, and run the TCK [3].
For the complete information, please allow me to mention the list of the TCK tasks needed to be done before the Jakarta EE release can be finished [4].
Thank you,
Jan
[1] https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run
[2] https://youtu.be/nnD1KMvh0to
[3] https://wiki.eclipse.org/TCK:Build_From_Jakarta_EE_TCK_Repo_And_Run#Jenkins_Pipelines
[4] https://github.com/orgs/eclipse-ee4j/projects/14
_______________________________________________
jakartaee-tck-dev mailing list
jakartaee-tck-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakartaee-tck-dev
_______________________________________________
ee4j-pmc mailing list
ee4j-pmc@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/ee4j-pmc
|
