Repository navigation
make CI cache more reliable #34435
Description
#34333 bumped bowser to a version that introduced a problem in oC (sharing not possible)
CI did not catch the issue because the old bowser version came from the cache. See #34433, that PR fails (correctly) because it disables the cache.
So currently we are not sure what versions of libs we are testing. The bug surfaced only after the QA tarball was build (I guess using none or an other cache than the CI) and was used in other tests for federation sharing (sharing from the federation server does not work).
Two things need to be done to improve the situation and help to test what we fly and fly what we test:
- we need to move away from caching the final dirs - to caching the package manager cache
example is here: https://github.com/owncloud/files_primary_s3/blob/master/.drone.yml#L75-L79 - automatically run all smoke tests after every tar ball build. E.g. we could have a nightly job that downloads the current tarballs and runs all smoke tests on it. Or the build of the tarball itself can happen on drone. Drone builds the tarball, unpacks it again, runs all smoke tests and if all is fine uploads the tarball.
Reacted by Paurakh Sharma Humagain
Activity
ownclouders commentedon Feb 11, 2019
GitMate.io thinks the contributor most likely able to help you is @PVince81.
Possibly related issues are #23455 (Make chunk cache ttl configurable), #23506 (ceph ci issues), #33329 (Make then steps more specific), #28166 (Cache in filecache), and #12873 (Make installer deletable).
patrickjahns commentedon Feb 11, 2019
You can start with a nightly test repository (similar to litmus / smashbox ) and do the following:
PVince81 commentedon Mar 11, 2019
PR here #34700
@patrickjahns can you confirm that this is the same thing ? if yes please close