Release 20.2.0

avito-tech · Feb 29, 2024 · d988fc2 · d988fc2
1 parent 2db0157
commit d988fc2
Show file tree

Hide file tree

Showing 4 changed files with 19 additions and 4 deletions.
diff --git a/Samples/Android/CodeSnippets/docker_compose/docker-compose.yaml b/Samples/Android/CodeSnippets/docker_compose/docker-compose.yaml
@@ -1,13 +1,13 @@
 version: '3'
 services:
   emcee-queue-service:
-    image: avitotech/emcee-queue:20.1.0
+    image: avitotech/emcee-queue:20.2.0
     container_name: emcee-queue-service
     ports:
       - 41000:41000
 
   queue-worker:
-    image: avitotech/emcee-worker:20.1.0
+    image: avitotech/emcee-worker:20.2.0
     env_file:
       - emcee-worker.env
     depends_on:

diff --git a/Samples/Android/CodeSnippets/k8s/emcee-queue-deployment.yaml b/Samples/Android/CodeSnippets/k8s/emcee-queue-deployment.yaml
@@ -15,7 +15,7 @@ spec:
     spec:
       containers:
         - name: emcee-queue
-          image: avitotech/emcee-queue:20.1.0
+          image: avitotech/emcee-queue:20.2.0
           imagePullPolicy: IfNotPresent
           ports:
             - containerPort: 41000
diff --git a/Samples/Android/CodeSnippets/k8s/emcee-worker-deployment.yaml b/Samples/Android/CodeSnippets/k8s/emcee-worker-deployment.yaml
@@ -16,7 +16,7 @@ spec:
     spec:
       containers:
         - name: emcee-worker
-          image: avitotech/emcee-worker:20.1.0
+          image: avitotech/emcee-worker:20.2.0
           imagePullPolicy: IfNotPresent
           resources:
             requests:

diff --git a/Sources/ScheduleStrategy/README.md b/Sources/ScheduleStrategy/README.md
@@ -43,6 +43,21 @@ to fiinsh its set of tests, while the most of destinations will be idle.
 }
 ```
 
+### Time weighted
+
+To address downsides of `equallyDivided` splitter strategy `timeWeighted` uses estimated tests time duration retrived from test history service.
+In order to make buckets more compact, set up test history service in queue and specify `timeWeighted` in test arg file. If test history hasn't
+been set up in queue or there are no sufficient data time-weighted splitter fallbacks to equally divided splitter.
+In large scale deployments you can prevent buckets granularity by specifying minimal bucket time (0 if not set).
+
+```json
+{
+    "scheduleStrategy": {
+            {"testSplitterType": {"type": "timeWeighted"}, "minBucketTime": 60}
+    }
+}
+```
+
 ### Progressive 
 
 A smarter technique that, in theory, combines the positive sides of each schedule strategy above and attempts to solve the problem when