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
Currently, we store snapshots of TestSuitesSource as ZIP archive on S3backend. Orchestrator creates a single volume with content from selected snapshots of TestSuitesSource. If there are several execution run against similar snapshots, we create (or re-use existed one) volume for each run.
Also, we have additional use cases with reading these snapshots -- to show public tests. But this use-case can be moved to fetch stage if we resolve a problem with choosing a specific test to be public.
Idea to duscuss
In general, we use content of snapshots only as volume for docker agents.
Maybe store it as volumes? But how it can be stored on S3?
Or we can add kind of cache: pre-create volumes for latest fetched snapshots of TestSuitesSource
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Overview
Currently, we store snapshots of
TestSuitesSourceas ZIP archive onS3backend.Orchestratorcreates a single volume with content from selected snapshots ofTestSuitesSource. If there are several execution run against similar snapshots, we create (or re-use existed one) volume for each run.Also, we have additional use cases with reading these snapshots -- to show public tests. But this use-case can be moved to fetch stage if we resolve a problem with choosing a specific test to be public.
Idea to duscuss
In general, we use content of snapshots only as volume for docker agents.
TestSuitesSourceBeta Was this translation helpful? Give feedback.
All reactions