Disable handling of OVERRIDES_DIR / /overrides in product tests#12153
Conversation
bea5a1b to
23ed484
Compare
Edit: these are removed during image creation already, so we should be fine. |
260e945 to
b9dcd20
Compare
b978ff4 to
dbf8b39
Compare
|
There still is |
dbf8b39 to
c9f1d73
Compare
|
@findepi were those overrides applied at build time? |
they should be. there was a bunch of images where build-time created /overrides and applied them, and didn't remove these override files. |
|
This should work after upgrading to docker-images v63. @ebyhr is taking care of it. |
This seems unused in product tests. Moreover, `apply-all-site-xml-overrides /overrides` is done as part of Docker images build process (see `docker-images` repo), so it seems we would be applying same overrides twice.
c9f1d73 to
5b1a9c0
Compare
|
rebased |
| @@ -1,14 +1,15 @@ | |||
| #!/usr/bin/env bash | |||
There was a problem hiding this comment.
Why not to drop it all together?
There was a problem hiding this comment.
I guess to be sure that we do not have overrides in one of the base images
There was a problem hiding this comment.
To be sure no-one tries to use mechanism that we're decomissioning.
Otherwise it could be possible that test run with a different configuration than expected.
There was a problem hiding this comment.
Removal should be a follow-up sometime later.
This seems unused in product tests.
Moreover,
apply-all-site-xml-overrides /overridesis done as part ofDocker images build process (see
docker-imagesrepo), so it seems wewould be applying same overrides twice.