Skip to content

docs(rfc): stovepipe record step design - #394

Open
mnoah1 wants to merge 1 commit into
mainfrom
mnoah1/record-step
Open

docs(rfc): stovepipe record step design#394
mnoah1 wants to merge 1 commit into
mainfrom
mnoah1/record-step

Conversation

@mnoah1

@mnoah1 mnoah1 commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

Design proposal for the record step outlined in stovepipe's workflow.md

@mnoah1
mnoah1 marked this pull request as ready for review July 16, 2026 19:33
@mnoah1
mnoah1 requested review from a team, behinddwalls and sbalabanov as code owners July 16, 2026 19:33
Following the extension rule "identity in, resolve internally," the Hooks contract takes a thin greenness identity rather than a controller-assembled external payload:

```
Notify(ctx, GreennessRef{Queue, URI, Project}) error

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we may want to have this as a separate RFC for Hook and hooks could anything including notifications so we may want to name it agnostic of the function it serves

(queue, uri, project)
```

`project` is empty for whole-repository greenness and is a stable project id in Phase 2. The key is derivable from identity the controller already holds, so storage requires no query by attribute or secondary index.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it records the status at the given commit? how do we answer the question of what is prev or next green commit for a given commit? how would that work? should that be a separate rfc?

For a delivery carrying build id `B`:

```
1. Load Build B.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why Build? why not the request? Shouldn't the buildsignal already capturing the status of request?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants