Skip to main content

Introduction

The project setup is described in a model that can be found and loaded into the μRadiant in the .nsproject folder.

The following scripts are expected to be present, if they are not you can check the migration guide or getting started.

  • scripts
    • expand_project_setup.nss
    • harvest_project_setup.nss

Project

  • project/scripts
    • release.nss
    • set_version.nss

Software Project

It will create multiple .nss scripts depending on your setup.

If you are using angular it will generate the following scripts:

  • project/scripts
    • start_<environment.name>_services.nss
    • stop_<environment.name>_services.nss
  • project/space-app/scripts
    • build_angular_frontend.nss - when using angular
    • serve_angular_frontend.nss
    • build_space_app.nss - builds the ear
    • expand.nss
    • harvest.nss
    • start_<environment.name>_services.nss
    • stop_<environment.name>_services.nss

Pipeline

The only pipeline currently supported is the Jenkins pipeline.

Stages

The currently supported stageTypes are:

stageTypesExplanation
AnalyzeThe analyze stage is for analyzing the model of your application and send this information to the prime radiant.
BuildThe build stage builds you application.
CustomThe custom stage allows you to have a completely custom implementation of a stage.
DeployThe deploy stage will push your artifacts to a specified location depending on conditions.
ExpandThe expand stage expands your application and clean harvests to check if there are no rogue files.
ReportThe report stage will run through the quality gates.
TestThe test stage is currently empty, but is a placeholder for integration testing.
Validatethe validate stage will do the model validation of the project setup and your software project(s).

Environments

The environments are used to either run your application locally or define other environments. Each environment has an environment override file where you can specify the necessary data that environment.

Services

The services specifies the runtime of an artifact. This has a one-to-one relationship with an artifact.

Artifacts

Artifacts are produced by the software project(s) or are external artifacts.