| Re: [jakarta.ee-spec.committee] where to host TCK jobs |
Bill, the job you pointed to is intended for use by anyone that wants to test an implementation. The job that runs all the standalone TCKs nightly is https://ci.eclipse.org/jakartaee-tck/job/standalonetck-nightly-build-run/ These use EPL licensed builds. There are corresponding EFSL licensed TCK jobs on ci.eclipse.org as well. Once those downloaf locations are settled, they should be producing results we can refer yo. -- Ed Bratt -------- Original message -------- From: Bill Shannon <bill.shannon@xxxxxxxxxx> Date: 7/26/19 4:14 PM (GMT-08:00) To: Jakarta specification committee <jakarta.ee-spec.committee@xxxxxxxxxxx> Subject: [jakarta.ee-spec.committee] where to host TCK jobs David brought up today about where TCK jobs should be hosted. Since the API jar files represent part of the spec, it's important that the API jar files pass at least the signature tests in the TCK for the spec. Depending on how much "implementation" exists in the API classes, it may be valuable for them to pass the entire TCK when combined with some Compatible Implementation. To this extent, having jobs to test the API jar files as part of the specification project seems reasonable and appropriate. I agree with David that doing the full TCK testing of a Compatible Implementation should be done by a job related to that Compatible Implementation. And in fact GlassFish, which is a Compatible Implementation for many of the specs, includes a job to run the TCKs for many of the specs: https://jenkins.eclipse.org/glassfish/view/cts/job/standalone-tck-certification/ So I agree: - The specification projects should test that the APIs are correct. - The implementation projects should test that the implementation is correct. And that's mostly what we have today. Some of the specification project jobs may be testing more than they need to, and that's something that could be refined in the future, taking into account the amount of implementation that's in the API classes. There are some projects that aren't following this approach for hosting the TCK jobs, and we'll need to adjust those in the future. _______________________________________________ jakarta.ee-spec.committee mailing list jakarta.ee-spec.committee@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee |