0
Fork 0
mirror of https://github.com/project-zot/zot.git synced 2024-12-16 21:56:37 -05:00
zot/test
Andrei Aaron 8553712613
chore: upgrade trivy to v0.55.2 and update the logic of waiting for zot to start in some jobs (#2685)
chore: upgrade trivy to v0.55.2, also update the logic of waiting for zot to start in some jobs

Seems like there's an increate in the time zot requires to start before servicing requests.
From my GitHub observations it is better check using curl instead of relying on hardcoded 5s or 10s values.

The logic in .github/workflows/cluster.yaml seems to be old and out of date.
Even on main right now there is only 1 our of 3 zots actualy running.
The other 2 are actually erroring: Error: operation timeout: boltdb file is already in use, path '/tmp/zot/cache.db'
This is unrelated to this PR, I am seeing the same issue in the olders workflow runs still showing the logs

Signed-off-by: Andrei Aaron <aaaron@luxoft.com>
2024-09-30 10:37:53 -07:00
..
blackbox chore: upgrade trivy to v0.55.2 and update the logic of waiting for zot to start in some jobs (#2685) 2024-09-30 10:37:53 -07:00
cluster chore: update image-spec and dist spec to 1.1.0 (#2255) 2024-02-20 13:27:21 +02:00
dex feat: use the "zot" namespace for the authentication url (#1947) 2023-10-20 15:30:56 +03:00
gc-stress chore: update image-spec and dist spec to 1.1.0 (#2255) 2024-02-20 13:27:21 +02:00
images test: add test images build instructions and stacker.yamls (#2249) 2024-02-15 13:49:25 +02:00
scale-out feat(cluster): Add support for request proxying for scale out (#2385) 2024-05-20 09:05:21 -07:00
scripts fix: ci 'TLS check' job is broken (#1970) 2023-10-27 10:39:04 -07:00