In this example we assume 7.0.19.
- Check beforehand that this version does NOT exist in staging else bump the version
- Go to GlassFish CI
- Log in
- Open glassfish_1-build-and-stage
- Click Build with parameters in menu
RELEASE_VERSION
=7.0.19
USE_STAGING_REPO
=false
(uncheck)- click [Build] button
- Wait for it to finish successfully
- Drill down into this build e.g. build 79
- Click Console Output in menu
- Ctrl+F 'orgglassfish', to find release ID, e.g.
Created staging repository with ID "orgglassfish-1230"
, remember this forSTAGING_RELEASE_ID
in a later step In case the release ID is not in the log (sometimes it just isn't, we don't know why), use go to jsftemplating_1_build-and-stagehttps://ci.eclipse.org/glassfish/view/JSFTemplating/job/jsftemplating_1_build-and-stage/buildLIST_FIRST
=true
(check)- click [Build] button In the output, look for a line like the following:
[INFO] orgglassfish-1352 CLOSED org.glassfish.main:glassfish-main-aggregator:7.0.19
- Verify that 7.0.19 is present in staging
- Verify that a new 7.0.19 branch is created
- Run the TCKs against the staged build at https://ci.eclipse.org/jakartaee-tck/view/EFTL-Certification-Jobs-10/
- Run the platform TCK
- Run the standalone TCK
- Wait for it to finish successfully
- Open 3_staging-to-release
- Click Build with parameters in menu
STAGING_RELEASE_ID
=orgglassfish-1352
- click [Build] button
- Wait for it to finish successfully
- Verify that it's present in Maven Central (usually takes few minutes now)
- If everything is OK, then merge 7.0.19 branch into master via PR
- Delete the 7.0.19 branch after merge
- Upload the new release to the Eclipse download folder.
Go to glassfish_copy-staging-to-downloads
- Enter the version to copy; 7.0.19
- click [Build] button
- Create the release on Github: https://github.com/eclipse-ee4j/glassfish/releases click "draft a new release"
- Create the release on Eclipse: https://projects.eclipse.org/projects/ee4j.glassfish click "create a new release"
- Create the release on Glassfish.org. Do a PR for the master branch with:
- an update for the website in
docs/website/src/main/resources
:- in
download_gf7.md
, create a section for the new version at the top, based on the previous version. Update the info based on the release notes in github, e.g. https://github.com/eclipse-ee4j/glassfish/releases/tag/7.0.19 - in
download.md
, replace information in the "Eclipse GlassFish 7.x" section at the top with info for the new version indownload_gf7.md
- in
README.md
, add a new piece into "Latest News", with the date of the release in Github, based on the info indownload.md
- in
- with an update for the docs:
- Update the property
glassfish.version.7x
with the released version in docs/pom.xml
- Update the property
- an update for the website in
- Create a new Eclipse GlassFish Docker Image - follow Eclipse GlassFish Docker Image Wiki