Manage Sequences

Trigger new sequences

To trigger new sequences, head to the environment view. There you can find the button “Trigger a new sequence”. This button can also be found on the sequences view and redirects you to the the environment view.

For sequences you have the possibility to choose from three sequence types:

• Delivery - This triggers the delivery sequence as defined in the shipyard.
• Evaluation - This triggers the Keptn default evaluation sequence.
• Custom - Trigger any other sequence defined in the shipyard, except the delivery and evaluation sequences.

After you have selected the desired sequence type, service, and stage click on “Next” to define the details of your sequence.

Trigger a delivery

Mandatory fields:

• Image - The image name that is going to be deployed.
• Tag - The version tag of the image.

Optional fields:

• Labels - Additional labels that will be used in Bridge for displaying additional info.
• Values - Values in JSON format, for the new artifact to be delivered. They can be used for the configuation of helm-service.

Trigger an evaluation

For triggering an evaluation, you can choose beween two variants to select the evaluation timeframe:

• Timeframe
• Start / end date and time

Timeframe

For the timeframe, there are no mandatory fields.

Fields:

• Timeframe - Takes hours, minutes, seconds, milliseconds and microseconds. Defines the timeframe from the given start date and time (or current date-time if not given) where an evaluation is performed. Defaults to 5 minutes and has a minimum duration of 1 minute.
• Start at - Defines the start date and time from when the evaluation is performed.
• Labels - Additional labels that will be used in Bridge for displaying additional info.

Special considerations:

• If you set a timeframe but no start date, the evaluation is performed on the previous timeframe span. This is the only case where evaluations are performed on data from the past.
• When a start date is specified, the evaluation is performed from this point to an end date. The end date can be specified or is calculated from the timeframe value.
• Please note: If the timeframe is calculated to an end date too far into the future, evaluation sequences might fail depending on the configured SLI provider.

Start / end date

Mandatory fields:

• Start at - Defines the start date and time from when the evaluation is performed. Must be before the end date.
• End at - Defines the end date and time until when the evaluation is performed. Must be after the start date.

Optional fields:

• Labels - Additional labels that will be used in Bridge for displaying additional info.

Trigger a custom sequence

Custom sequences are automatically fetched from the shipyard. All sequences that are defined in this file, except delivery and evaluation, are then selectable as sequences in the sequence dropdown.

Mandatory fields:

• Sequence - The custom sequence to be triggered.

Optional fields:

• Labels - Additional labels that will be used in Bridge for displaying additional info.

Sequence view

The sequence view shows all executed sequences for the selected project.

The list on the left side gives a brief overview of all sequences and can be filtered. By clicking one of the sequences, the detail for it opens. This detailed view shows every executed task for the selected sequence in a specific stage. It includes information like the related events, the result, and the payload.

For evaluation sequences, the Bridge also provides a link to the evaluation board. For delivery sequences, the Bridge provides a link to the deployed artifact.

When opening the detail, the default selection is the last executed stage. Select a different one by clicking on the stage name in the timeline.

Filtering

Filtering provides a way of getting a better overview of the sequences. Filter by using the search bar or by selecting the items from the filter list.

Filters can apply to:

• Service - all services created for the project
• Stage - all stages defined in the shipyard file of the project
• Sequence - all sequences defined in the shipyard file of the project
• Status - sequences can have the status active, succeeded, or failed. Active state includes all sequences that have not been completed with a finished event yet.

Pausing and resuming sequences

Running sequences can be paused. The button to trigger pausing is on the top right of a list entry or the detail view. Clicking the button halts the running sequence until it is resumed. Please note: Any running task is going to finish before the service pauses the sequence. That means that the Bridge may show a paused state, but the task list is still running.

Aborting sequences

Running and paused sequences can be aborted. The buttons to trigger abortion is located on the top right of a list entry or the detail view. Clicking the button stops the running sequence entirely. After cancellation, it is not possible to restart it in any way. Please be certain before aborting it. Please note: Any running task is going to finish before the service aborts the sequence. That means that the sequence may be still in progress directly after aborting. It may take some minutes until the sequence has a completed state. An example can be seen below. In this case the sequence is marked as succeeded, but some tasks are still in progress.