MAIA Software, Open FAQ

General

This FAQ is about common questions related to concepts, definitions, licensing etc.

We also have a FAQ for technical issues related to the usage of the MAIA Software application,  MAIA Support

Licensing

Accordion Sample Description

Accordion Sample Description

Accordion Sample Description

Accordion Sample Description

Definitions

A build is the processed content of a specific block, for example a block that has been compiled.

The output from a build can be stored as artifacts in an artifact repository or in a file system.

The result of the build is displayed on the Builds: Show page , and if the build is delivered the content of the build is presented in a delivery report.

A build can be processed in a build session, and can also have test runs and test results registered
to it.

See "What is a Block?"

A block is a collection of files in a repository, or a collection of other blocks.

A collection of files is called a component block, and a collection of blocks is called a suite block.

All blocks share the same base properties:
· Their content is version controlled.
· They are stored in one or more software repositories.
· They contain one or more tracks (branches) for parallel development.
· The events connected to a block can be tracked. For example, commits, issues, issue status, changes, builds, deliveries, test runs and changes in block configurations.
· Each block in MAIA has a dashboard that summarizes the latest events on the block.
· The access to block information is restricted between groups.

A block has properties unique to the block:
· It can contain meta data needed to build a collection of blocks, if the block is a suite. For example, a list of sub blocks in the configuration file of the block.
· When a block is built, the content of the build is defined at build time, when the meta data is processed. This allows for dynamic builds.
· If the block is suite, its build can contain both components, suites and suites-of-suites.