Explore Pipelines and Topology

After deploying neuralbank-backend, inspect how Tekton materializes CI/CD and how OpenShift represents the application in the topology view.

Open the Pipelines Console

  1. Log in to the OpenShift Console.

  2. Select project user1-neuralbank.

  3. In the sidebar, go to Pipelines (or CI/CD → Pipelines).

Locate the PipelineRun

  1. On the PipelineRuns tab, sort by Started (most recent first).

  2. Identify a run referencing neuralbank-backend.

If you see no runs, confirm that the webhook trigger was created. The CronJob automatically sets up Gitea webhooks for each user’s repositories.

Pipeline Definition

The pipeline is defined in the template’s tekton/pipeline.yaml:

apiVersion: tekton.dev/v1
kind: Pipeline
metadata:
  name: neuralbank-backend-pipeline
spec:
  params:
    - name: git-url
    - name: git-revision
      default: main
    - name: image-name
  tasks:
    - name: git-clone
      taskRef:
        name: git-clone
    - name: maven-build
      taskRef:
        name: maven
      runAfter: [git-clone]
    - name: build-image
      taskRef:
        name: buildah
      runAfter: [maven-build]
    - name: deploy
      taskRef:
        name: openshift-client
      runAfter: [build-image]

Review Pipeline Tasks

Open the PipelineRun and examine each task:

Task What to look for

git-clone

Repository and revision cloned; check the Gitea URL (uses internal service URL)

maven-build

Java build; mvn logs and generated artifact

build-image

Container image build with Buildah; image pushed to internal registry

deploy

Deployment update on OpenShift; verify the new image reference

For each task, open the logs and confirm it ended in Succeeded.

Webhook Configuration

Pipelines are triggered by Gitea webhooks. The TriggerBinding uses internal service URLs for reliability:

apiVersion: triggers.tekton.dev/v1beta1
kind: TriggerBinding
metadata:
  name: neuralbank-backend-binding
spec:
  params:
    - name: git-url
      value: http://gitea-http.gitea.svc.cluster.local:3000/$(body.repository.full_name).git
    - name: git-revision
      value: $(body.after)

This ensures webhook-triggered builds work reliably without TLS certificate issues.

Use the Topology View

  1. In the console, open the Topology view for project user1-neuralbank.

  2. Locate the backend Deployment (circular icon with status ring).

  3. Click the node to open the side panel: Pods, Services, Routes, and events.

Return to Developer Hub

  1. Open Developer Hub.

  2. Locate component neuralbank-backend in the catalog.

  3. From the entity card, check the CI/CD tab showing Tekton pipeline status.

Summary

You followed a PipelineRun task by task, understood the webhook configuration, validated deployment state in Topology, and related the component to its entry in Developer Hub.