Closed kishansagathiya closed 6 years ago
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
I can't test these changes by updating the tenant, because what update tenant is similar to oc apply
. They use something called three way merge, where they compare current config and asked config and based on that make changes.
PR now available for testing: Launch in OpenShift.io and click the update tenant button
from @rupalibehera
IMO we should also check how much time we require for subsequent builds after removing content-repository does that make any difference
@rupalibehera I don't see any change in build times
PR now available for testing: Launch in OpenShift.io and click the update tenant button
PR now available for testing: Launch in OpenShift.io and click the update tenant button
@hrishin have tested latest changes with a few builds
This is one such successfully built commit https://github.com/kishansagathiya/app-test-1/commit/2ed2570ce6d4a7172e2d5a96bf33092b36ab5dfd