Executions

Overview on how to track Executions on the Analyze section of Typhoon Test Hub.

An Execution is created whenever a Job or Pipeline is started. You can see the most important information about executions in the Executions table (Figure 1).

Figure 1. Executions table

The Executions table shows the following information:

  1. Status of execution :
    • - failed
    • - stopped by specific user or Hub
    • - passed
    • - waiting in a queue to start
  2. ID unique execution identifier
  3. Name of the job from which the execution is created
  4. Duration of execution
  5. Time when execution started
  6. Time when execution finished

Pipelines can be expanded to show the list of stages and jobs inside stages.

Figure 2. Extended Pipeline example

You can open any generated Allure report by clicking on the Allure icon (). Also, you can focus on a generated report by clicking on the Report button ().

You can change the number of items in the table in the Navigator tab.

When all executions are shown in the table, you can filter reports by column. An example of this is shown in Figure 3.

Figure 3. Execution table with activated filters

Execution details

Figure 4. Details for the selected Execution

In the Details section, you can find the following tabs:

  1. Overview tab: Here you can see basic information and redirect by clicking on links like Job86 to that job in the jobs page and see more information.
  2. Definition tab: Displays definition of the Job or Pipeline of the selected Execution.
  3. Console output tab: Displays logs from execution.
  4. Artifact tab: Contains a table of generated artifacts.
  5. Reports tab: Contains reports generated for the selected execution.
Note: If button is visible next to the link like Job86, it will enable user to see that specific version of the Job that was used by current execution. In this case, jobs page will be opened in a new tab of the browser, Job86 will be preselected, and Changes history tab will be focused with that specific Job's version selected. Here user can choose any other version and compare changes during time, which can help with determining potential problem that occurred during Job execution. Button will be visible if Agent, Job, Pipeline, Computer or Setup changed since the selected Execution was created.

If the selected item is a Pipeline, then Details contains an additional Definition tab, where pipeline definitions can be seen.

Finally, the Overview tab contains basic information and a visualized pipeline.

Figure 5. Visualized pipeline

Definition tab

Data shown in the definition tab for the selected Execution presents an overview of the Job/Pipeline used for creating selected Execution, as well as an overview of the Agent, Computer and Setup used by the selected Execution.

Figure 6. Definition tab data preview

Running execution

When an execution is made, it will wait until the setup is free and until the agent is available. As soon as that happens, the execution starts and the status icon changes to a spinning icon () until the execution ends. While the execution is running, the Console Output tab will display logs in real time (Figure 7). Afterwards, you can observe all console logs.

Figure 7. Console output tab

If an execution finished with the status PASSED, the execution status will become , and if it finishes with status FAILED, the status will become . The status becomes if the button is clicked to stop the execution. Any execution that is not queued or running can be deleted by clicking on the button. Logs of the selected Execution can be downloaded by clicking on the button.

Deleting execution

Clicking on the Delete execution opens a confirmation dialog. Content of the dialog will be different depending on the type of the execution.

Figure 8. Job execution delete

If the Reports box is checked, then all Reports connected to this Job execution will be deleted.

If the Artifacts box is checked, then all Artifacts connected to this Job execution will be deleted.

Figure 9. Pipeline execution delete

If the Executions box is checked, then all nested executions of this Pipeline will be deleted. When this option is clicked additional information in the dialog will be available.

Figure 10. Pipeline execution delete additional information in the dialog

If the Reports box is checked, then all Reports connected to the nested execution of this Pipeline execution will be deleted.

If the Artifacts box is checked, then all Artifacts connected to the nested executions of this Pipeline execution will be deleted.