Starting with Bleriot (6.4) release, Snapshot processes one Application at a time. It is therefore no more required to:
- Snapshot all Applications from all Systems at the same time;
- Snapshot an Application that does not evolve any more. It is also possible - yet with limitations (cf. dedicated paragraph below)
- to Snapshot old versions or builds of an Application and to incorporate them in the natural flow of the Snapshots.
Snapshot configuration settings are:
- Assignment of a Capture Date
- Capture Date is designed to hold the date the source code of the Application was produced, independently from the Snapshot computation date
- Capture Date lets you process old source code and assign the resulting Snapshot with the date "it should have been processed"
- Capture Date lets you synchronize Snapshots from different Applications, that were computed on different date yet that pertain to source code from the same day
- Capture Date is unique for an Application in a Dashboard Service
- Assignment of Version information
- Version information is designed to hold the Application and Module version information, such as a build number, an SCM label, etc.
- Version information is used in the CAST Engineering Dashboard
- When generating a Snapshot on a single Application, you can enter the Version information to apply to the Application. Module-level Version information will be automatically inherited from the Application-level value. You can edit Version information afterwards to fine-tune the values.
- When generating a Snapshot on multiple Applications at the same time, through a triggering at the Delivery Unit level or the Dashboard Service level, you can enter the Default Version information to apply to all the Applications. Application- and Module-level Version information will be automatically inherited from the Default Version information value. You can edit Version information afterwards to fine-tune the values.
- Assignment of a Snapshot Label
- Label information is designed to hold contextual information about the Snapshots themselves
- Label information is used in the CAST Engineering Dashboard
- It is highly recommended to keep the Label unique for an Application in a Dashboard Service to preserve compatibility with legacy GUIs.
Snapshot configuration supports the following post-processing updates:
- Snapshot Labels can be changed any time: they will be taken into account in the CAST Engineering Dashboard once reloaded
- Version information can be changed at any time: it will be taken into account in the CAST Engineering Dashboard once reloaded
- You need to explicitly update the version information for all Modules in the Application
- The Version information is used in the Quick Access page in the CAST Engineering Dashboard to simplify the selection of Snapshots to compare; information accuracy and readability is required
Snapshot configuration advanced settings are:
- Assignment of an enriched Capture Date with the addition of an Input Time instead of the default 00:00 value.
- Cf. Capture Date value setting - particular cases for use cases.
The limitation that forced you to compute Snapshot according to the chronological sequence has been removed.
However, use this capability only when required as it will leave the Analysis Service content in a "past" state: in the CAST Engineering Dashboard and the Discovery Portal, the Technical Context and the source code will be pertaining to the Application source code that was last analyzed.
It is therefore recommended to:
- Try to end the computation sequence with the latest source code
- As a workaround, you can re-analyze the latest source code (no need to generate the Snapshot) of the Application
- If not possible, the end-users have to be warned about the situation
Impacts of Capture Date update on selections for action and exclusion
Selection for action (Action Plan)
When changing the sequence of Snapshots (e.g.: to move a Snapshot in the past), the Action Plan considers the selection is reset to the latest Snapshot. Obviously, it can not consider the selection took place in the past and should have been taken care of since then.
Selection for exclusion
When changing the sequence of Snapshots (e.g.: to move a Snapshot in the past), the exclusions are still impacting the snapshot results, even if the Snapshot is moved before another Snapshot where exclusions were not defined.