Skip to content

plugin-catalog.md

Latest commit

 

History

History
52 lines (37 loc) · 2.05 KB

plugin-catalog.md

File metadata and controls

52 lines (37 loc) · 2.05 KB
Raw

rhdh-plugin-catalog layout

Files to update

Location When to edit
.tekton/oci-plugin-build-pipeline.yaml Shared Pipeline; most PLRs use pipelineRef
.tekton/plugin-catalog-index-*-push.yaml Inline pipelineSpec (catalog index)
.tekton/plugin-catalog-builder-*-{push,pull}.yaml Inline pipelineSpec (catalog builder)
.tekton/*-push.yaml (many components) Usually spec.params only when migration adds pipeline params
.tekton/*-pull.yaml Same when present
.tekton/generatePipelineRunsForPlugins.sh Heredoc for regenerated PLRs + *.Containerfile
.tekton/updateToStableBranch.py Version renames only — not Konflux migrations

Plugin PLRs with pipelineRef: oci-plugin-build-pipeline inherit task wiring from the shared pipeline; add PLR spec.params when migrations require explicit pipeline parameters.

Regenerate

cd .tekton
./generatePipelineRunsForPlugins.sh -v <x.y.z> --nopush

Generator: new pipeline params

Add to the PipelineRun heredoc spec.params when oci-plugin-build-pipeline gains a param, e.g.:

  - name: enable-package-registry-proxy
    value: "true"

Do not embed full pipelineSpec in the generator.

Version naming (x.y.z → x-y)

generatePipelineRunsForPlugins.sh derives RHDH_XY_VERSION from -v x.y.z (e.g. 1.10.0 → 1-10). Use it everywhere; never hardcode 1- in generated paths.

Pattern Example for 1.10.0
PLR / Containerfile basename bcp-rbac-1-10-push.{yaml,Containerfile}
Konflux component / application bcp-rbac-1-10, rhdh-plugin-catalog-1-10
Target branch in CEL rhdh-1.10-rhel-9 (dots, not dashes)
Containerfile builder comment .tekton/plugin-catalog-builder-1-10-push.yaml

After regenerate, grep for stale -1-push (without minor version):

rg '-1-push' .tekton --glob '*.Containerfile'

A hit like plugin-catalog-builder-1-push.yaml means the generator heredoc still hardcodes 1- instead of ${RHDH_XY_VERSION}.