Continuous Integration
The jakartaee-platform CI is rooted at jakartaee-platform Jenkins
Key artifacts jobs are:
-
jakartaee-api release and stage all
- Builds a release of all jakartaee-api artifacts and stages them (Deprecated, probably broken)
-
jakartaee-api release and stage selected
- Builds a release of selected jakartaee-api artifacts and stages them (Preferred)
-
1_jakartaee-api-staging-to-release/
- Releases a staged relase to Maven Central using the repository ID, a value of the form jakartaplatform-NNN generated by the previous staging job.
Examples of the jakartaee-api release and stage selected
The following sections highlight the typical uses of the jakartaee-api release job.
We might want to do a release of just the jakarta.jakartaee-bom artifact to pickup service release updates in the component specifications. To do that:
- navigate to the https://ci.eclipse.org/jakartaee-platform/job/1_jakartaee-api-stage/
- Enter the RELEASE_VERSION, here shown as 11.0.0-RC3
- Check the STAGE_BOM checkbox
- Select the appropriate JAVADOC_LICENSE drop down value, EPL for non-final release, EFSL for final releases.
- Hit the Build button.
We might want to do a release of just the jakarta.jakartaee-core-api artifact as the first platform specification artifacts in a new major release, or to pickup service release updates in the component specifications. To do that:
- navigate to the https://ci.eclipse.org/jakartaee-platform/job/1_jakartaee-api-stage/
- Enter the RELEASE_VERSION, here shown as 11.0.1
- Check the STAGE_CORE_PROFILE checkbox
- Select the appropriate JAVADOC_LICENSE drop down value, EPL for non-final release, EFSL for final releases.
- Hit the Build button.
Release the jakarta.jakartaee-web-api and jakarta.jakartaee-api after a jakarta.jakartaee-core-api release
Suppose the jakarta.jakartaee-core-api has already been released with version 11.0.1 because the Core Profile was released first in the current major update of the platform, and it has had one service release. If the jakarta.jakartaee-web-api for the Web Profile and jakarta.jakartaee-api for the Platform are now ready to be released, this can be done as follows:
- navigate to the https://ci.eclipse.org/jakartaee-platform/job/1_jakartaee-api-stage/
- Enter the RELEASE_VERSION, here shown as 11.0.0
- Enter 11.0.1 for the jakartaee_core_api_version
- Check the STAGE_WEB_PROFILE checkbox
- Leave the jakartaee_web_api_version as ${RELEASE_VERSION}
- Check the STAGE_PLATFORM checkbox
- Select EFSL JAVADOC_LICENSE drop down value for a final releases.
- Hit the Build button.
