Snapshot generation options
Since Bleriot (6.4) release, a Snapshot is processing one Application at a time.
There is therefore two main triggering methods:
- Individual triggering of a Snapshot on a single Application
- Mass-triggering of Snapshots on many Applications
Last, a batch generation is also possible.
Individual triggering of a Snapshot on a single Application
This is the recommended way when only one Application has evolved.
This individual triggering is the best way to avoid artificial plateau in trend graphs and the loss of delta information that can be caused by a new Snapshot on an unchanged Application.
This individual triggering is the best way to avoid spending computing resources on unchanged Applications.
The individual triggering can be initiated from an Application node from the Delivery Units tree.
Mass-triggering of Snapshots on many Applications
The mass-triggering of Snapshots is useful when you need to process a batch of Applications at the same time.
Note this is a mass-triggering that leads to a Snapshot per Application. Snapshot Capture Date, Label, and Version information will be shared by all Applications. You can edit Version information afterwards to fine-tune the values.
The mass-triggering can be initiated from a Delivery Unit node and from a Dashboard Service node from the Delivery Units tree.
Batch triggering of a Snapshot on a single Application
The individual triggering of a Snapshot on a single Application is also possible in batch mode, using the CAST-MS-cli.exe executable.
- Get the syntax by running "CAST-MS-cli.exe" or "CAST-MS-cli.exe -help"
- Protect blank character with " around the character string
Capture Date setting
Bleriot release (6.4) introduced the concept of Capture Date for the Snapshots.
This new piece of information lets you enter and store in the AIP the date the source code was produced or captured. Indeed, the computation date of a Snapshot has everything to do with the operations of the AIP (when were you able to run the computation, based on the availability of resources such as a complete source code, CPU, etc.). It fails to inform the portal user of the moment in time at which you look at the Application quality and quantity. The Capture Date is designed to overcome this limitation.
Capture Date value setting - general cases
On a daily basis, you can follow the following guidelines:
- When processing an old version or release of the source code of an Application, please enter the version, or release, or revision date as the Snapshot Capture Date.
- When processing the current build every week or so, keep the default value (default is the current date, with default time information set to: 00:00).
Capture Date value setting - particular cases
Some circumstances may force you to follow different guidelines:
AIP Migration process
We recommend creating a Snapshot before and a Snapshot after the AIP migration process to visualize the impact of the migration on assessment results
To avoid creating the impression that an evolution is linked to the source code while the evolution is linked to the migration, it is also recommended to use the same date information for the Capture Dates of the pre- and -post migration Snapshots, yet using a slightly different time information
Thus, in the CAST Engineering Dashboard, the migration-related evolutions are shown as steps happening on the source code with identical Capture Date (indeed, time information is not visible in the CAST Engineering Dashboard).
When you want to process an Application multiple times a day, you can enter a Capture Date including both date and time information.
Simply update the default time information (00:00) with current time and keep the default Snapshot label ("Computed on YYYYMMDDHHMM").
The CAST Engineering Dashboard will show all the Snapshots under the same Capture Date, in the right sequence and with Snapshot labels available in tooltips to get more details about the exact date and time the Snapshot took place.
When you want to fine tune the configuration of your AIP and see the results in the CAST Engineering Dashboard to assess the best result, you may want to run multiple Snapshots on the same Application
Simply enter a different Capture Date, by entering the current time in the time information field.
This would ensure unique Capture Date.
The CAST Engineering Dashboard will show all the Snapshots under the same Capture Date, which is not an issue as this is a tuning action.