You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this Issue, I'd like to propose adding another event, artifact.flagged.
Our use case
We run tests that create messages like testSuiteRun.finished and testSuiteRun.finished. These tests ultimately are intended to validate whether some other system-under-test is in a healthy state. When a test completes, we would like to post a message, saying that a given "artifact" has been "flagged" with a passing or failing test.
Alternatives
While, internally, we have been using the rather generic name of "flagged", for our purposes, it would be fine with us to go to a more granular level and have the message instead be "Artifact.tested".
Message details
Roughly, we envision something that has identifers for the artifact, and identifiers for the test with its associated status (failed/passed/etc...)
The text was updated successfully, but these errors were encountered:
@dan-han-101 , this artifact.flagged event, do you think it is the same use case as the confidence label or maturity level terms I mentioned in my comment on this issue: #143 (comment) ?
Currently, an "artifact" has the following predicates: packaged, published, and signed.
In #143 - there is a discussion on adding
artifact.pulled
deleted
scanned
And in #144 - there is a discussion for adding
artifact.pushed
In this Issue, I'd like to propose adding another event,
artifact.flagged
.Our use case
We run tests that create messages like
testSuiteRun.finished
andtestSuiteRun.finished
. These tests ultimately are intended to validate whether some other system-under-test is in a healthy state. When a test completes, we would like to post a message, saying that a given "artifact" has been "flagged" with a passing or failing test.Alternatives
While, internally, we have been using the rather generic name of "flagged", for our purposes, it would be fine with us to go to a more granular level and have the message instead be "Artifact.tested".
Message details
Roughly, we envision something that has identifers for the artifact, and identifiers for the test with its associated status (failed/passed/etc...)
The text was updated successfully, but these errors were encountered: