Using the build platform Konflux (with hermetic builds supported) you must perform a full build of each Orchestrator plugin variant. Steps include: registering the plugin component in Konflux, submitting a build job (via Tekton pipeline) to build the OCI/artefact, generate SBOM, run scans (vulnerabilities, provenance) and verify that the produced artefact is correct and meets quality criteria. Also validate that the downstream (e.g., the overlay or plugin-catalog) picks up the artefact without issues. Log any failures, fix build config if required.

First step is in RHIDP-9745:

• include 4 new plugins in the https://github.com/redhat-developer/rhdh-plugin-export-overlays/blob/main/rhdh-supported-packages.txt
  • Ensure that each plugin variant (for the four plugins) is listed correctly with the appropriate identifiers,
  • version tags (BS 1.42.5)
  • and metadata so that the downstream build system picks them up.
  • Validate that the format matches existing entries and that no syntax/validation errors occur. After adding, commit and push changes.

Once that's done, in this issue we need to:

• sync change to downstream https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/pipeline_schedules (or run ./build/ci/sync-midstream.sh --no to pull in the new workspace and see local changes

• onboard to pyxis: ./build/scripts/generatePyxisConfigForPlugins.sh -v 1.9.0
• onboard new KRD components: ./build/scripts/generateKonfluxReleaseDataForPlugins.sh -v 1.next
• regen PLRs for the two packages: ./.tekton/generatePipelineRunsForPlugins.sh -v 1.next --regex orchestrator --trigger
• build in Konflux: https://konflux-ui.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/ns/rhdh-tenant/applications/rhdh-plugin-catalog-1/activity/pipelineruns?name=orchestrator
• check output in quay: ./build/scripts/checkPluginsExist.sh to verify new content
• re-run sync-midstream.sh to see if new metadata, plugin_builds/, or catalog-index content is created