Closed bconey closed 4 years ago
Updating the script to tolerate both type of image name inputs.
PR is ready for this fix : https://github.com/kabanero-io/kabanero-pipelines/pull/404
Fix is in 0.9.1-rc.3
@bconey - Hi Barbara, Thank you for looking after te verification and closure of this issue.
Moved beyond this failure in the build step, but now seeing a reference to "invalid reference format" in the push step
/bin/bash: line 2: params.docker-imagename: command not found
/bin/bash: line 2: params.docker-imagetag: command not found
[INFO] Application image URL = image-registry.openshift-image-registry.svc:5000/kabanero/kab60-java-spring-boot2:edb265436eb45cfd1a40894b799207a9189024bb/kab60-java-spring-boot2
[INFO] Running the script /scripts/image_registry_access_setup.sh ....
[INFO] The image registries that got added successfully to insecure list are = [ 'image-registry.openshift-image-registry.svc:5000' ]
[INFO] Signature will not be generated. The signed image repository is not set or does not match the target registry.
[INFO] Pushing image to registry...
invalid reference format
Step failed
Fix based on above issue mentioned by @bconey is in PR : https://github.com/kabanero-io/kabanero-pipelines/pull/408 Once it is merged it can be verified. cc: @kvijai82
Verified
Upgraded a cluster w/ a springboot2 app for which pipelines had been successful to use Kabanero 0.9.0 and then triggered a pipeline for that same application (used the existing webhook) and it failed in the build step with the following error