spec
spec copied to clipboard
cdevents
A common specification for Continuous Delivery events
The links spec introduced snake casing, instead of camel casing. So we should ensure that these get moved over to camel casing. These 3 are what I found: 1. *link_type*...
# Changes - define every fields `url` and `viewUrl` with `format: "uri"` as proposed in #191 - as the version of schema was with suffix `-draft`, I didn't update them...
I propose that the subject object within each event type definition is split into two objects - subject and predicate, where the new subject object would contain items that are...
The version field https://github.com/cdevents/spec/blob/main/spec.md#version specifies that it defines the version of the *specification*. Also the https://github.com/cdevents/spec/blob/main/spec.md#type-context specifies that is should contain the version of the *event*. When looking at a...
_This issue was raised as a result of a discussion during the CDEvents WG on Jan 30th, 2023_ These event subjects all represent _executions_ of some kind, as they can...
The documentation for pipelineRun.finished and taskRun.finished declares that the outcome shall be an enum with a limited set of values. The schemas declare these fields as free text strings though....
# Changes This PR addresses a missing field of, `outcome`, that should exist in the `build.finished` event. This follows the `outcome` of `taskRun.finished`, except that it utilizes an enum value...
# Changes # Submitter Checklist As the author of this PR, please check off the items in this checklist: - [ ] Has the [primer doc](https://github.com/cdevents/cdevents.dev/blob/main/content/en/docs/primer/_index.md) been updated if a...
With version 0.4, ticket's schema define type of some field (`priority`, `resolution`, `ticketType`) like: ```json "anyOf": [ { "type": "string", "enum": [ "low", "medium", "high" ] }, { "type": "string"...
We would like to identify and document the process for deprecating fields in CDEvents. We discussed this during [a working group](https://github.com/cdevents/community/blob/main/working-group-notes.md#oct-23rd-2023) and identified the following options: 1. Document in the...
