Skip to content

Jakarta EE TCK Jenkins jobs

Jump to bottom
Alwin Joseph edited this page May 10, 2019 · 19 revisions

Jakarta EE TCK Jenkins jobs

Jakarta EE TCK jobs uses the Jenkins OSS customized by the Eclipse Foundation team hosted at https://ci.eclipse.org/jakartaee-tck/ for the various build, release and run jobs. It uses the Jenkins pipeline setup based on the Jenkinsfile checked into the Jakarta EE TCK Github repository for running all kinds of jobs. The pipeline job is parameterized, which can take in multiple inputs from the user or upstream jobs and execute the required build/run stages in the pipeline. Various upstream jobs are created in the CJE instance which in turn use this Jenkins pipeline in master branch to trigger various kinds of jobs by passing appropriate input parameters.

There are 2 kinds of TCK bundles that gets created from the Jenkins Jobs. They are

  • Jakarta EE TCK bundle (Generated from Jakarta EE TCK Github repository)

    This is a single bundle (jakartaeetck.zip) containing the tests, scripts and configurations required to validate and confirm all technologies that are part of the Jakarta EE specification. This bundle is meant to be run with various Java EE compatible servers (like GlassFish, Payara, WebLogic, Wildfly etc). The default configuration stored in the bundle is used for running tests against GlassFish RI bundle. The tests typically run in various containers like EJB, Servlet, AppClient etc.

  • Standalone TCK bundles

    These are small and independent subset of tests along with the scripts and configurations required for validating a specific technology. The specific technology may or may not be part of the Jakarta EE specification. The default configurations stored in the bundle is used for running the tests against standalone RI implementation. For instance, JSON-B tck bundle can be used for running against Yasson standalone RI implementation. The various technologies for which the standalone TCK bundles gets generated are as follows:

    Generated from Jakarta EE TCK Github repository

    • CAJ
    • Concurrency
    • Connector
    • EL
    • JACC
    • JASPIC
    • JAXR
    • JAX-RPC
    • JAX-RS
    • JAX-WS
    • JMS
    • JPA
    • JSF
    • JSP
    • JSON-B
    • JSON-P
    • JSTL
    • JTA
    • SAAJ
    • SecurityAPI
    • Servlet
    • WebSocket

    Generated from repositories outside Jakarta EE TCK Github.

    • cditck-porting
    • ditck-porting
    • bvtck-porting
    • debugging-support-for-other-languages-tck
    • javamail-tck
    • jaf-tck

Job Summary

Job Name Trigger Type Frequency Report Link
publish-glassfish-bundle Automated Nightly NA
oracle-javaeects8-certification-full Manual Milestone builds Latest Report
oracle-javaeects8-certification-web Manual Milestone builds Latest Report
jakartaeetck-nightly-build Automated Nightly NA
jakartaeetck-nightly-run Automated Nightly Latest Report
jakartaeetck-nightly-run-web Automated Nightly Latest Report
jakartaeetck-certification Manual Milestone builds/Debugging failures Latest Report
standalonetck-nightly-build-run Automated Nightly Latest Report
standalonetck-certification Manual Milestone builds/Debugging failures Latest Report

Staging Job

  • publish-glassfish-bundle This job runs on a nightly basis and publishes the latest Eclipse GlassFish bundle built from EE4J_8 branch to the staging area in Eclipse download server. The latest bundle would be accessible here

Oracle JavaEE 8 CTS bundle related Jobs

These jobs are meant for certifying Eclipse GlassFish 5.1.0 against the Oracle Java EE 8 CTS certification bundle published by Oracle. These jobs are required to be run till the first release of Jakarta EE TCK bundle is released officially from Eclipse Foundation.

  • oracle-javaeects8-certification-full This job is meant for running the entire Oracle Java EE 8 CTS tests using the latest released bundle published by Oracle and available in the staging area against the latest Eclipse GlassFish full profile bundle built from EE4J_8 branch. This job is triggered manually on a need basis. The latest results would be published here. The details of the GlassFish Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

  • oracle-javaeects8-certification-web This job is meant for running the web profile related Oracle Java EE 8 CTS tests using the latest released bundle published by Oracle and available in the staging area against the latest Eclipse GlassFish web profile bundle built from EE4J_8 branch. This job is triggered manually on a need basis. The latest results would be published here. The details of the GlassFish Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

Jakarata EE TCK bundle related Jobs

The following jobs are used for building and running the Jakarta EE TCKs from Jakarta EE TCK Github Repository against Eclipse GlassFish RI.

  • jakartaeetck-nightly-build This job is meant for building the Jakarta EE TCK bundle (bundle used for certifying all JavaEE/JakaratEE Technologies). It builds the Jakarta EE TCK bundle (jakartaeetck.zip) and publishes it to the nightly staging area. This job is triggered on a daily basis and does not require any user intervention. It runs the samples suite to validate the built bundle.

  • jakartaeetck-nightly-run This job is meant for running the entire Jakarta EE TCK tests using the latest nightly TCK bundle available in the staging area against the latest GlassFish full profile bundle built from EE4J_8 branch. This job is triggered on a daily basis and does not require any user intervention. The latest results would be published here. The details of the GlassFish Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

  • jakartaeetck-nightly-run-web This job is meant for running the web profile related Jakarta EE TCK tests using the latest nightly TCK bundle available in the staging area against the latest GlassFish web profile bundle built from EE4J_8 branch. This job is triggered on a daily basis and does not require any user intervention. The latest results would be published here. The details of the GlassFish Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

  • jakartaeetck-certification This job is meant for certifying milestone builds like (RC1, RC2 etc.) or for validating a custom development build to run a subset of tests for validation and debugging failures. This is not triggered periodically and used only on a need basis. This job is parameterized and if its required to run confirm only a subsets of technologies, then those alone can be selected and run.

Standalone TCK bundle related Jobs

The following jobs are used for building and running the various standalone technology TCKS against Eclipse GlassFish RI.

  • standalonetck-nightly-build-run This job runs on a nightly basis and builds all the available standalone technology TCKs in full profile mode from scratch and runs it against the latest nightly GlassFish full bundle built in master branch. The job publishes the standalone TCK bundles to the nightly staging area available here. The latest nightly run results are available here. The details of the GlassFish Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

  • standalonetck-nightly-build-run-web This job runs on a nightly basis and builds all the available standalone technology TCKs in web profile mode from scratch and runs it against the latest nightly GlassFish Web bundle built in master branch. The latest nightly run results are available here. The details of the GlassFish Web Bundle used identified by its unique Git Commit ID and the JakartaEE TCK bundle used for the run, are mentioned in the build description for easy tracking.

  • standalonetck-certification This job is meant for certifying milestone builds like (RC1, RC2 etc.) or for validating a custom development build to run a subset of tests for validation and debugging failures. This is not triggered periodically and used only on a need basis. This job is parameterized and if its required to run confirm only a subsets of technologies, then those alone can be selected and run.

Clone this wiki locally