epam/edp-headlamp

Add pipelines page, fix pipeline run page, sync ui

Closed this issue · 0 comments

We need to create the 'Tekton' sub-section within the Configuration section. The 'Tekton' sub-section should include a 'Pipelines' tab. The 'Pipelines' tab must display a list of Tekton Pipelines sourced from Tekton EDP Delivery. The columns to be displayed in the list should be discussed further. When a user clicks on a Pipeline name, they should be able to view either the YAML or graphical presentation of the pipeline.

Acceptance Criteria
A 'Tekton' sub-section is added to the Configuration section.
The 'Tekton' sub-section contains a 'Pipelines' tab.
The 'Pipelines' tab displays a list of Tekton Pipelines.
Columns to be displayed in the list are defined and agreed upon.
Clicking on a Pipeline name allows the user to see either the YAML or graphical presentation of the pipeline.
Implementation Plan

  1. Add the 'Tekton' sub-section to the Configuration section.
  2. Implement the 'Pipelines' tab within the 'Tekton' sub-section.
  3. Integrate the list of Tekton Pipelines from the provided URL.
  4. Discuss and define the columns to be displayed in the Pipelines list.
  5. Implement functionality to display either YAML or graphical presentation of the pipeline when a Pipeline name is clicked.

The following improvements and bug fixes are required in the "Pipelines" section of the KubeRocketCI Portal:

  1. If a Tekton task is not in a running state, return the name of the steps instead of an empty page.
  2. Enable the 'Details' section in pipelinerun to show details about the task. Migrate the logic from Tekton Dashboard to KubeRocketCI Portal.
  3. Fix the bug where switching between pipeline tasks retains the previous task set.

h4. Implementation Plan

  1. Review the current implementation of the "Pipelines" section in the KubeRocketCI Portal.
  2. Modify the logic to return the name of the steps if a Tekton task is not in a running state instead of showing an empty page.
  3. Implement the 'Details' section in pipelinerun to display detailed information about the task. Migrate the necessary logic from Tekton Dashboard to KubeRocketCI Portal.
  4. Investigate and fix the bug where switching between pipeline tasks retains the previous task set.
  5. Test the changes to ensure the improvements are working as expected and the bug is fixed.

h4. Acceptance Criteria

  • Names of the steps are returned if a Tekton task is not in a running state.
  • The 'Details' section in pipelinerun shows detailed information about the task.
  • The logic from Tekton Dashboard is successfully migrated to KubeRocketCI Portal.
  • The bug where switching between pipeline tasks retains the previous task set is fixed.
  • The changes are tested and verified for correct behavior.