Nort: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 45: Line 45:


<pre>
<pre>
$ ./bin/operations
NOMBP2:events ovidiu$ operations
Nova Ordis Release Tools
Nova Ordis Release Tools


Line 58: Line 58:
Commands:
Commands:


     install-release-tools <project-home-directory>
     install [-f|--force]
 
    release <snapshot|minor|major|patch|"version-string">
 
        Makes a release by incrementing the release information appropriately, running all tests, building the final
        artifact and installing the artifact in the appropriate repository. If a version string is used, the string
        is checked for consistency. The release process will fail if the version string is invalid or represents an
        older version than the current version.


        Install the release tools into the 'bin' subdirectory of the specified project home directory.
    test - internal release tools testing shortcut. Advanced users only.
        A target directory qualifies as "project home directory" if it has a Maven pom.xml in it.


Installation:


     install [-f|--force]
     ./src/main/bash/operations install-release-tools <project-home-directory>
</pre>
 
        The installation functionality can currently only be accessed from the original repository.
        'install-release-tools' installs the release tools into the 'bin' subdirectory of the specified project home
        directory. A target directory qualifies as "project home directory" if it has a Maven pom.xml in it. If an
        older version of the release tools is already installed, 'install-release-tools' will upgrade in place.


<font color=red>Under Development.</font>
Per-Project Configuration:


<pre>
    Create an operations.conf in the directory the release tools were installed into and configure local project
./bin/test
    properties.
</pre>
</pre>
Tests experimental functionality.

Revision as of 08:36, 12 May 2016

Internal

Overview

A set of bash scripts that know how to interact with Maven and the Maven configuration. They provide extended operational capabilities for Nova Ordis projects: runtime wrappers, building artifacts to be distributed, local and remote installation, etc. A customized copy of these scripts is installed under the ./bin directory for each project.

In the future, the utilities will gain the capability of driving Go projects as well, offering a unified command line interface for Java and Go projects.

GitHub


https://github.com/NovaOrdis/novaordis-release-tools

Installation

Update novaordis-release-tools from GitHub and then:

.../novaordis-release-tools/install <project-home-dir>


What it does not do and it should

Usage

In-line help is available with:

operations

which is the original name of the script and it should be available in the ./bin subdirectory.

The latest output:

NOMBP2:events ovidiu$ operations
Nova Ordis Release Tools

Usage:

    <command> [global-options] <command-arguments> | operations [global-options] <command> <command-arguments>

Global Options:

    -v | --verbose - verbose execution.

Commands:

    install [-f|--force]

    release <snapshot|minor|major|patch|"version-string">

        Makes a release by incrementing the release information appropriately, running all tests, building the final
        artifact and installing the artifact in the appropriate repository. If a version string is used, the string
        is checked for consistency. The release process will fail if the version string is invalid or represents an
        older version than the current version.

     test - internal release tools testing shortcut. Advanced users only.

Installation:

    ./src/main/bash/operations install-release-tools <project-home-directory>

        The installation functionality can currently only be accessed from the original repository.
        'install-release-tools' installs the release tools into the 'bin' subdirectory of the specified project home
        directory. A target directory qualifies as "project home directory" if it has a Maven pom.xml in it. If an
        older version of the release tools is already installed, 'install-release-tools' will upgrade in place.

Per-Project Configuration:

    Create an operations.conf in the directory the release tools were installed into and configure local project
    properties.