README
¶
Build issue detection
Detector discovers confirmed validation issues from a build. It returns build issues, not a complete view of build state.
Issue values are defined in the domain model. A validation task is a logical validation operation. A validation unit is an identifiable piece of work within a task.
Within a validation queue, TaskID and UnitID together identify the validation condition. Repeated reports of the same condition use the same pair across builds. UnitID is empty for a task-wide issue.
Nonterminal detection returns issues discoverable at that time and may repeat or omit previously reported issues. Reported issues remain part of that build's accumulated results; later omissions do not retract them. Detection does not mark issues as handled.
A successful detection after build completion must return the complete cumulative issue set for the build within the queue's relevant validation scope, including issues returned by earlier calls. The result must be complete independently of whether earlier calls finished persisting their results. An empty terminal result is valid only if the build has no reportable issues. If the complete set cannot be determined, detection must return an error rather than report success. Implementations decide when a failure qualifies as a reportable issue.
Detectors must support concurrent calls. Dependency failures return plain errors; issue results returned with an error must not be used.
DetectorFactory resolves the detector for a validation queue.
Documentation
¶
Overview ¶
Package buildissue defines confirmed-issue discovery for active or completed builds, independently of build status polling.
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
This section is empty.
Types ¶
type Detector ¶
type Detector interface {
Detect(ctx context.Context, buildID entity.BuildID) ([]entity.BuildIssue, error)
}
Detector discovers issues retained in a build's accumulated results. Nonterminal calls may repeat or omit issues returned earlier. A successful terminal call must return the complete cumulative issue set for the build, including issues returned by earlier calls. Return an error if that set cannot be determined. Implementations must be concurrency-safe and must not consume evidence. Return plain dependency errors; issue results returned with an error must not be used.
type DetectorConfig ¶
type DetectorConfig struct {
// QueueName identifies the queue.
QueueName string
}
DetectorConfig identifies the queue whose issue detector is requested.
type DetectorFactory ¶
type DetectorFactory interface {
For(cfg DetectorConfig) (Detector, error)
}
DetectorFactory resolves a detector for a validation queue.
Source Files
Directories