Hi all,
As I'm in a process of releasing a new version of Woodstock, I documented the release process in the description of this Jenkins job - all-projects_1_build-and-stage:
Here's a copy of the documentation:
- Run with Dry run enabled - Will push a tag to the repository on Github
- Fetch and checkout the new tag locally
- Build the tagged version and test it locally
- Run with Dry run disabled - Will release to Maven Central staging area
- Publish from the Maven Central staging area (Separate access needed, request via Eclipse GitLab
- Create a release in Github based on the release tag
- Merge the release branch to master, delete the release branch
- Create a release record, add PROJECT selected in parameters as a version suffix (e.g. 1.0.1-hk2-extra)
The release process was changed because of the changes in Maven Central and decommissioning of Eclipse Maven staging repository.
The job all-projects_1_build-and-stage should be used to for performing releases of all GlassFish repositories, except GlassFish itself (e.g. Grizzly, HK2, Woodstock, maven plugins, etc.).
Currently, no other job is needed. I disabled the other 2 jobs (all-projects_3_staging-to-release and all-projects_manage_staging_repos), they are not going to be used any longer.
All the best,Ondro Mihalyi
Director, Jakarta EE expert
