only push PR images to quay if PR label is present

[gebhardtr]

No description provided.

[jameswnl]

@gebhardtr the pr-deployment failed because pr-963 image tag is not there in quay

error in cluster: Back-off pulling image "quay.io/ansible/wisdom-service:pr-963"

[gebhardtr]

Looks like it was this too (#968), preventing it from making it to the push?

Last metadata expiration check: 0:00:18 ago on Tue Apr 30 21:25:02 2024.
Argument 'nginx/common' matches 2 streams ('1.22', '1.24') of module 'nginx', but none of the streams are enabled or default
Unable to resolve argument nginx/common
Error: Problems in request:
broken groups or modules: nginx/common
error building at STEP "RUN dnf module install -y nginx/common": error while running runtime: exit status 1

[goneri]

The Image Build issue is resolved, you can rebase your PR.

[jameswnl]

PR Deployment created in https://console-openshift-console.apps.stage2-west.v2dz.p1.openshiftapps.com/k8s/ns/wisdom-pr-963/apps~v1~Deployment

wisdom-service url: https://wisdom-service-wisdom-pr-963.apps.stage2-west.v2dz.p1.openshiftapps.com

[jameswnl]

PR Deployment created in https://console-openshift-console.apps.stage2-west.v2dz.p1.openshiftapps.com/k8s/ns/wisdom-pr-963/apps~v1~Deployment

wisdom-service url: https://wisdom-service-wisdom-pr-963.apps.stage2-west.v2dz.p1.openshiftapps.com

[jameswnl]

PR Deployment created in namespace wisdom-pr-963

Look up the wisdom-service url in the cluster

[jameswnl]

PR Deployment created in namespace wisdom-pr-963

Look up the wisdom-service url in the cluster

[jameswnl]

we don't need this anymore because we are moved to Konflux build. and PR images there are set to expire after 5 days.
if we want to skip PR image build, we have to modify the tekton workflow https://github.com/ansible/ansible-ai-connect-service/blob/main/.tekton/ansible-ai-connect-service-pull-request.yaml#L227

[gebhardtr]

thanks @jameswnl! I resolved the conflict; since the workflow is still present (the triggers are commented out), can we merge this anyway just in case we uncomment the triggers? (at least until we delete the workflow entirely).

[jameswnl]

thanks @jameswnl! I resolved the conflict; since the workflow is still present (the triggers are commented out), can we merge this anyway just in case we uncomment the triggers? (at least until we delete the workflow entirely).

it is actually already disabled. it's currently only available for workflow_dispatch -- just keeping this to give Konflux a week or two to warm-up

[gebhardtr]

right, the triggers are commented out but the workflow is still present; let's merge this until we delete it (and we can have a record for how to do it in the future).

[jameswnl]

right, the triggers are commented out but the workflow is still present; let's merge this until we delete it (and we can have a record for how to do it in the future).

sounds good to me :)