messages/schemas/koji-build.test.queued.yaml

$id: koji-build.test.queued
$schema: http://json-schema.org/draft-07/schema#

description:
    Testing has been queued, but not yet started.
    This is an optional message.

properties:
    contact:
        $ref: contact.json
    run:
        $ref: run.json
    artifact:
        $ref: rpm-build.json
    pipeline:
        $ref: pipeline.json
    test:
        $ref: test-common.json
    generated_at:
        $ref: common.json#/properties/generated_at
    version:
        $ref: common.json#/properties/version
    system:
        type: array
        items:
            $ref: system.json

required:
    - contact
    - run
    - artifact
    - pipeline
    - test
    - generated_at
    - version

type: object
Make all `$id`s into relative references (#67) As discussed in #67, these being absolute URIs that do not resolve successfully breaks validation with recent versions of jsonschema, because when it runs into a ref it will try to access the referred schema via the URI. Making the top-level `$id`s into relative references is allowed by the JSON Schema drafts, though it's "recommended" that they be valid absolute URIs. It also ought to be handled as we expect by validators, as when the `$id` is a relative reference they are supposed to resolve it with reference to the current base URI, which should be the base URI of the "entire document", which should be wherever they opened the file from. Hence they should be able to follow the structure. This makes validation work on F30 at least, haven't confirmed that it works on older jsonschema yet but it ought to. Signed-off-by: Adam Williamson <awilliam@redhat.com> 2019-08-08 17:41:31 -07:00			`$id: koji-build.test.queued`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`$schema: http://json-schema.org/draft-07/schema#`

			`description:`
			`Testing has been queued, but not yet started.`
			`This is an optional message.`

			`properties:`
(0.2.1) use contact instead of ci and gate array Resolves issue #42 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com> 2019-03-20 15:54:32 +01:00			`contact:`
Rename "ci" schema to "contact" to be more general The "ci" schema has been renamed to "contact" and extended with the "docs" attribute so that we can share the system and team information across all gating and testing messages. 2018-09-17 11:18:00 +02:00			`$ref: contact.json`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`run:`
			`$ref: run.json`
			`artifact:`
Use a single schema for koji builds & brew builds Let's share the schema for koji builds and brew builds as they are (and should be) basically identical. This removes some duplication as well as ensures we keep rpm build artifacts consistent between upstream and downstream. 2018-09-11 11:52:04 +02:00			`$ref: rpm-build.json`
Changes for version 0.2.0 of the spec Notable changes include: - move of test related attributes to new test array - move error related attributes to error array - move recipients to new notification array - add new pipeline array - move of thread_id to pipeline.id This is not a backwards compatible change. Rebased on top of 1.1.3 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com> 2019-02-13 18:18:03 +01:00			`pipeline:`
			`$ref: pipeline.json`
			`test:`
			`$ref: test-common.json`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`generated_at:`
Fragments are JSON Pointers or named schemas, not both 2020-11-19 21:15:33 -05:00			`$ref: common.json#/properties/generated_at`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`version:`
Fragments are JSON Pointers or named schemas, not both 2020-11-19 21:15:33 -05:00			`$ref: common.json#/properties/version`
Add "system" to running, queued and error test messages Complete test result messages have required "system" field. Related running, queued and error messages should define same "system" values. This is required by Greenwave which in addition to item + type + testcase values, also distinguishes test results by unique scenario + system_architecture + system_variant values. For example, if there is a test result with status RUNNING and undefined "system", it would be considered missing by Greenwave until test a completed (or error) result with undefined "system" is published. A message with any other "system" value would be considered as a result of a different test. 2022-04-05 16:03:03 +02:00			`system:`
			`type: array`
			`items:`
			`$ref: system.json`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00
			`required:`
(0.2.1) use contact instead of ci and gate array Resolves issue #42 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com> 2019-03-20 15:54:32 +01:00			`- contact`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`- run`
			`- artifact`
Changes for version 0.2.0 of the spec Notable changes include: - move of test related attributes to new test array - move error related attributes to error array - move recipients to new notification array - add new pipeline array - move of thread_id to pipeline.id This is not a backwards compatible change. Rebased on top of 1.1.3 Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com> 2019-02-13 18:18:03 +01:00			`- pipeline`
			`- test`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00			`- generated_at`
Add missing version field Required version field was missing in some messages. Signed-off-by: Miroslav Vadkerti <mvadkert@redhat.com> 2018-09-15 12:59:28 +02:00			`- version`
Add koji build schemas and examples 2018-08-20 15:58:04 +02:00
			`type: object`