Page tree
Skip to end of metadata
Go to start of metadata

Valid for AIP Console ≥ 1.26.

Introduction

AIP Console provides two delivery modes:

ModeDescriptionBenefitsDisadvantages
Standard, with version history

This mode is the standard mode that has been used in all releases of AIP Console and is the default for AIP Console ≥ 1.26:

  • Source code for a given version is:
    • either uploaded as a ZIP file and is then unpacked in the upload folder on the relevant AIP Node
    • or accessed directly from the specified source code folder
  • Source code is then compressed and copied into the Delivery folder, therefore retaining version history
  • Source code is then copied to the Deploy folder and is analyzed from there.

The copying of source code multiple times into various different folders can reduce overall version processing time (i.e. total time taken from specifying the source code to generating the snapshot) and increase the amount of disk space required for source code storage.

  • Version history is retained - i.e source code/configuration from previous versions. Enables previous versions to be set as the current version and re-analyzed.
  • Ability to control the version onboarding process in steps (accept and set as current version are not automatically completed in an advanced onboarding scenario).
  • Possible to change from ZIP to source code folder (or vice versa) as the method of source code deployments once a first version has been delivered.
  • Overall application onboarding time may be slower, especially for larger applications.
  • More disk space is required to store the source code in multiple locations.
Rapid, without version history

This mode was introduced in AIP Console 1.26 and provides a faster delivery process by skipping some steps related to the management of source code for analysis:

  • Source code for a given version is:
    • either uploaded as a ZIP file and is then unpacked in the upload folder on the relevant AIP Node
    • or accessed directly from the specified source code folder
  • Source code is is analyzed from the above locations.

Therefore:

  • Source code is never compressed and copied into the Delivery folder, therefore no version history is retained
  • Source code is never copied to the Deploy folder

Skipping two copy actions to move the source code to different folders can significantly improve overall version processing time (i.e. total time taken from specifying the source code to generating the snapshot) especially when the source code volume is very large.

In addition, when an advanced onboarding scenario is used instead of a one-shot standard onboarding, the version will be automatically accepted and set as the current version (see image below), simply because no versions are retained. This also improves overall version processing time:

Click to enlarge

  • Overall application onboarding time may be quicker, especially for larger applications, due to reduced number of times the version source code needs to be copied and moved around.
  • Less disk space required for source code storage.
  • Less steps to action in an advanced onboarding scenario (accept and set as current version are automatically completed).
  • Version history is NOT retained - i.e source code/configuration from previous versions. It is therefore not possible to set a previous version as the current and re-analyze it.
  • Not possible to change from ZIP to source code folder (or vice versa) as the method of source code deployments once a first version has been delivered
  • No exclusion management supported in current release

Choosing a delivery mode

The delivery mode can only be chosen when an application is first created and it is not possible to change to a different delivery mode once the choice has been made. The choice is made in the application creation dialog box (see also Add a new Application and Add a new Application for CAST Imaging). By default the Manage Version History option is ticked - this means that standard mode with version history will be used. Unticking the option will cause the rapid mode without version history to be used:

UI differences in rapid delivery mode

When an application is created using rapid delivery mode, there are various slight differences that indicate the mode is active:

Banner

In the Application - Overview panel a banner will be displayed to indicate that rapid delivery mode is active for the Application:

Exclusions

When adding a new version, the Exclusions panel (see Standard onboarding - add a new Version - deliver code - generate snapshot in the wizard is not available. This is currently a known issue which will be fixed in a future release:

  • No labels