Skip to content

README.adoc

Latest commit

 

History

History
51 lines (29 loc) · 1.74 KB

README.adoc

File metadata and controls

51 lines (29 loc) · 1.74 KB

ORM Releases

Table of Contents

Where is the information

If you’re looking for information about how to release Hibernate ORM, see MAINTAINERS.md

If you’re looking for information about how releases are implemented technically, read on.

How it works

Releases are triggered as a Jenkins pipeline. Hibernate ORM also publishes SNAPSHOT releases using an automated Jenkins pipeline, which is triggered on a merge to the main branch. This job requires no user interactions.

When a release job is started, the job coordinates with the unified Hibernate release scripts in a number of stages and steps, calling tasks on this module’s Gradle script and leveraging JReleaser configuration.

Note
 Snapshot releases are not relying on JReleaser but on built-in Gradle publish plugin. See the Jenkinsfile.

At a high-level, this process:

  • builds and verifies the individual modules

  • produces artifacts and publishes them

  • tags the release

  • updates the website

This process has a number of "outputs"…​

Release Artifacts (jar)

Release artifacts are published to Sonatype OSSRH (aka, Maven Central). For each module, we publish:

  • The "main" jar

  • The sources jar

  • The javadoc jar

Gradle Plugin

The Gradle plugin gets published to Gradle’s Plugin Portal.

Documentation

All documentation for the release is generated, assembled and then published to the documentation server.