Release validation

Release validation records what happened when Sysand Index tried to load a published release with the Sysand and Syside tools used by the index. This page lists the stored validation data and the public badge states.

For the conceptual overview, see Release validation. For upload-time archive requirements, see KPAR archive validation.

Validation attempt data

Each validation attempt belongs to one project release and stores:

Field	Meaning
Status	Internal validation result: pending, passed, syside_warnings, standard_issues, or errored.
Syside version	Syside version used for the attempt, when available.
Sysand version	sysand version used for the attempt, when available.
Diagnostic summary	Counts by severity and category.
Diagnostics	Structured diagnostic rows recorded from Syside.
Error message	Infrastructure or tool error text for attempts that could not complete.
Started at	When the attempt row was created.
Finished at	When the attempt reached a terminal status.

Diagnostic rows can include:

• category: parser, validation, or sema

• severity: diagnostic severity reported by Syside

• message: diagnostic message

• code: diagnostic code, when provided

• filename, line, and col: source location, when provided

File paths from the temporary validation workspace are shown relative to the extracted project root when possible.

Validation process

For each validation job, Sysand Index:

1. Creates a pending validation attempt.

2. Fetches the release archive from the configured Sysand index root when one is configured.

3. Extracts the archive into a temporary workspace.

4. Runs sysand sync.

5. Reads package and dependency sources with sysand sources.

6. Falls back to scanning .sysml and .kerml files when sysand sources returns no sources.

7. Calls Syside to load the discovered sources.

8. Stores structured diagnostics, tool versions, the final status, and a finish timestamp.

Infrastructure exceptions are stored as terminal errored validation attempts. The worker job itself is not retried automatically.

Public badge states

Project and release pages show a public badge derived from the active validation job or latest validation attempt.

Badge	Source condition	Meaning
Not validated	No validation attempt and no active validation job	No validation attempt has been recorded for this release.
Validation queued	Active validation job with queue status todo	A validation job is waiting to run.
Validation running	Active validation job with queue status doing	A validation job is currently running.
Validation pending	Latest attempt has internal status pending and no active job is visible	A validation attempt started but has not finished.
Validated	Latest attempt has internal status passed	Validation completed without recorded warnings or errors.
Validation warnings	Latest attempt has warning diagnostics and no error diagnostics	Validation completed with warnings, but no recorded errors.
Validation errors	Latest attempt has error diagnostics or internal status standard_issues	Validation completed with one or more recorded errors.
Could not validate	Latest attempt has internal status errored	The validation attempt could not complete.

Active queued or running jobs take precedence over older completed validation attempts. When the active job finishes, pages show the latest completed result.

Revalidation

Sysand Index queues release validation after a release upload transaction commits. Staff can also queue validation for project releases from the staff background jobs page.

Bulk staff queueing skips releases that already have active queued or running validation jobs.