Client-Server communication

Search…

This is an advanced section for those curious about the communication between client and server. This section is not needed to use Testground, but to understand the protocol between client and server.

Build
POST /build
Build sends a mime/multipart build request to the daemon. A build request comprises the following parts:
Part 1 (Content-Type: application/json): composition JSON (see below)
Part 2 (Content-Type: application/zip): test plan source
Part 3 (optional, Content-Type: application/zip): linked SDK
The request is the same kind multipart mime message archive your email administrator knows and loves so well. With this archive in hand, the plan is POST'ed the Testground daemon.
Run
POST /run
A Run request consists of a composition JSON (see below)
Composition JSON
1
{
2
  "composition": {
3
    "metadata": {
4
      "name": string,
5
      "author": string,
6
    },
7
    "global": {
8
      "plan": string,
9
      "case": string,
10
      "total_instances": int,
11
      "builder": string,
12
      "build_config": object,
13
      "runner": string,
14
      "run_config": string,
15
    },
16
    "groups": [
17
      "id": string,
18
      "resources": {
19
        "memory": string,
20
        "cpu": string,
21
      },
22
      "instances": {
23
        "count": int,
24
        "percentage": float,
25
      },
26
      "build":
27
      "run":
28
    ],
29
  },
30
}
Copied!
Collect outputs
POST /outputs
1
{
2
  "runner": string,
3
  "run_id": string,
4
}
Copied!
Terminate Jobs
POST /terminate
1
{
2
  "runner": string,
3
}
Copied!
Healthcheck
POST /healthcheck
1
{
2
  "runner": string,
3
  "fix": bool,
4
}
Copied!

Runtime environment (runenv)

Getting started

Last modified 1yr ago

Copy link

Contents