You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
assert"testprojectname/"insteps["cloudharness-base"]['image_name'], "cloudharness-base image should be overridden and take the main name"
65
65
assert"cloudharness-base-debian"notinsteps, "cloudharness-base image should not be included"
66
66
assert"cloudharness-frontend-build"insteps, "cloudharness-frontend-build image should be included as dependency"
67
-
assert"cloud-harness/"insteps["cloudharness-frontend-build"]['image_name'], "cloudharness-frontend-build image is not overridden and should keep the cloud-harness prefix"
67
+
assert"testprojectname/"insteps["cloudharness-frontend-build"]['image_name'], "cloudharness-frontend-build image is not overridden"
assert"cloud-harness"inbuild_argument, "Cloudharness flask image should have cloud-harness in its path"
126
-
assertbuild_argument=="CLOUDHARNESS_FLASK=${{REGISTRY}}/cloud-harness/cloudharness-flask:${{CLOUDHARNESS_FLASK_TAG}}", "Dependency is not properly set in the build arguments"
125
+
assert"testprojectname"inbuild_argument, "Cloudharness flask image should have cloud-harness in its path"
126
+
assertbuild_argument=="CLOUDHARNESS_FLASK=${{REGISTRY}}/testprojectname/cloudharness-flask:${{CLOUDHARNESS_FLASK_TAG}}", "Dependency is not properly set in the build arguments"
assertvalues[KEY_TASK_IMAGES]['cloudharness-base'] =='reg/testprojectname/cloudharness-base:1', "Cloudharness base image is overridden, so takes the main project name prefix"
0 commit comments