Get a test-results upload
Returns where an upload is (waiting for its bundle, received, ingested or skipped) and the problems ingestion found in it. Requires read access to the upload’s test collection.
Authorizations
An API key, sent as Authorization: Bearer <key>. An organization admin creates one in the Trunk app under Settings → Developer → API Keys and chooses the permissions it holds. A new key starts with no permissions: it can read merge queues but change nothing in them, and it cannot get a Dynamic CI plan. Each endpoint that needs a permission names it in its description; the Dynamic CI plan endpoints need Generate Dynamic CI plans.
Path Parameters
Response
The upload
A test-results upload: where it is, and what ingestion found.
Where an upload is. awaitingData: Trunk has not read the bundle. Past expiresAt on the create, it was never uploaded or could not be read. received: ingestion has started and not finished. Ingestion retries for about 10 minutes, so an upload still received with updatedAt more than 15 minutes old was not ingested and will not change. ingested: ingestion has recorded the upload. Its results and defects are written just after, so defects can still grow for a few seconds; each one moves updatedAt. If writing them fails, the upload stays ingested with its results incomplete. An invalid defect names a part of the bundle that was left out. skipped: it was read, but so many of its tests failed that Trunk treated the run as an infrastructure failure and stored no results.
awaitingData, received, ingested, skipped "ingested"