-
Task
-
Resolution: Done
-
Critical
-
None
-
None
-
8
-
False
-
-
False
-
-
-
RHDH COPE 3278, RHDH COPE 3279, RHDH COPE 3280, RHDH COPE 3281, RHDH COPE 3282
Per discussion with rbean@redhat.com and rh-ee-oaljalju today (gemini notes), the best path thru Konflux publishing of individual OCI artifact plugins is:
- use a cached build env container, like we have for the RHDH GL runners
- script a process to build the image in konflux & publish the image to registry.stage.redhat.io (to avoid needing a prodsec exception for using a quay.io base image)
See existing environment for RHDH at:
And existing RHDH plugin catalog build env at:
Can we merge these into a single image, and publish them using a pipeline for https://konflux-ui.apps.stone-prod-p02.hjvn.p1.openshiftapps.com/ns/rhdh-tenant/applications/rhdh-plugin-catalog-1/components/plugin-catalog-1 ?
Images will be pushed to https://quay.io/rhdh/plugin-catalog-builder
------------
Summary:
base image ( https://quay.io/rhdh/plugin-catalog-builder ) is created with:
- https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/blob/rhdh-1-rhel-9/build/containerfiles/builder.Containerfile
- https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/blob/rhdh-1-rhel-9/.tekton/plugin-catalog-builder-1-push.yaml?ref_type=heads
published to reg.stage using https://gitlab.cee.redhat.com/rhidp/rhdh-plugin-catalog/-/blob/rhdh-1-rhel-9/build/scripts/kfuxRelease.sh#L54 (using -v 1.8.0 --builder --auto or -v 1 --builder --auto for 1.next)- registry.stage.redhat.io/rhdh/plugin-catalog-builder:1.9
- registry.stage.redhat.io/rhdh/plugin-catalog-builder:1.8
Then, tekton pipelines use a reg.stage image for the base image:
and a shared pipeline:
Done:
get exception in RHIDP-9620 for reg.stage or quay.io use- regenerate all the pipelines with --trigger-existing (
RHIDP-9616) - verify that pipelines no longer fail with violation
- blocks
-
-
- Closed
-
- clones
-
-
- Closed
-
- is blocked by
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned on
