Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-6173

Create Shipwright BuildRun detail page

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Normal Normal
    • openshift-4.11
    • None
    • UI
    • 2
    • False
    • False
    • RHDP-320 - Integrated CI/CD experience with OpenShift platform
    • 0
    • Undefined
    • Not Supported
    • ODC Sprint 219, ODC Sprint 220

      Description

      As a user, I want check my Shipwright BuildRun status and logs.

      Acceptance Criteria

      1. Create Shipwright BuildRun detail page which shows multiple tabs:

      1. Detail tab with custom right hand side column (see below)
      2. YAML
      3. "TaskRuns" with related resources filtered by label
      4. NO Environment tab in the first version
      5. Logs tab only if PipelineRun "Logs" tab could be reused ??
      6. Events tab only if events could be easily filtered by a label (See also PipelineRun "Events" tab)

      2. Show infos about the build (see https://shipwright.io/docs/api/buildrun/) on the right hand side:

      1. NO Metrics in the first version
      2. Status (status.conditions)
      3. Message (status.conditions)
      4. "Build" (back reference spec.buildRef.name)
      5. Same infos from the Build detail page, but from spec.buildSpec:
        1. "Strategy" as resource link (spec.strategy) to BuildStrategy or ClusterBuildStrategy
        2. "Git repository" (spec.source.url)
        3. Git commit if available ?!?
        4. "Context dir" (spec.source.contextDir) if defined
        5. "Dockerfile" (spec.dockerfile) if defined
        6. "Builder image" (spec.builder.image, a docker.io image name for example)
        7. "Credentials" as Secret resource link (spec.source.credentials)
        8. "Output to" (spec.output.image, an URL)
          1. If image URL links to the internal registry, link the ImageStream
          2. If not, show the URL as string
        9. "Credentials" as Secret resource link (spec.output.credentials)

      Additional Details:

      1. High Level Design

            cjerolim Christoph Jerolimov
            cjerolim Christoph Jerolimov
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: