Nort User Manual

Internal

• Nova Ordis Release Tools

Concepts

Concepts

Release

A NORT release consists in a sequence of interactions with the local project work area, the build system metadata, and various external source code and binary repositories. All types of releases end with the creation of a set of valid release artifacts and the publishing of the artifacts into their corresponding repositories. At the end of the release process, the work area is automatically updated to support the development iteration for the next release.

Release Types

Custom

For syntax details see the release command.

Release Artifacts

Binary Distributions

The recommended technique to build complex binary distributions is to add a dedicated "release" module to the project and let the Maven assembly plug-in to handle the process. The details are described in the "Building a Maven Complex Release Artifact" article.

If a project has a binary distribution, NORT will publish it in the Maven repository, under the "release" module of the project.

release

The command queries or modifies release information metadata for the current work area and performs the sequence of steps required to release. For more details about what a release is, and what those steps are, see the "Release" section.

To query the current release information, execute:

release info

To write a new release metadata into the current work area, use:

release major|minor|patch|snapshot|<custom-release-string>

The release increment does the following:

• Increments release metadata in the local workarea.
• Runs all tests.

If at least one test fails, the command restores the previous release metadata states, reports and fails.

If all tests succeed what now?

build

The command creates releasable artifacts (binary distributions or libraries, depending on the nature of the project) for the current version. If the build process is successful, the artifacts are stored in the build area ("target" directory, for Maven) of the current work area.