Release of FESA Software

During release of FESA software using the FESA Eclipse plug-in several conditions apply. The release is currently (07/16) steered using the information from the state-element. In the following is described what is considered during release.

Development/Test Release

If a release is done for development/test purposes the release procedure has less checks. In the FESA preferences the expert settings may be used. SVN repository check, automatic synchronization/generation of the source code, automatic build/compilation of the sources and the export of the FESA design to the database may be skipped.

The directory for a FESA deploy-unit delivered in development mode is named as the deploy-unit trailed by -d. The reason is that a release of a FESA deploy-unit should not directly overwite a possibly productive FESA deploy-unit.

It is currently (07/16) planned to allow exporting a FESA design during a release for development/test purposes to a development/test database.

Productive Release

The release of FESA software for productive purposes has certain restrictions compared to the release for test purposes:

• The FESA software must be under version control and must be synchronized with the SVN repository.
• The FESA design will be automatically synchronized (source code generation).
• The FESA software will be compiled.
• The FESA design will be exported to the database.

The settings of the FESA expert preferences will not be considered.

If any of the restrictions cannot be fulfilled the release procedure fails.

It is currently (07/16) planned to allow exporting a FESA design during a release for productive purposes to a productive database.

-- SolveighMatthies - 12 Jul 2016