-
Notifications
You must be signed in to change notification settings - Fork 50
Description
When collecting data for ' bowtie-trends,' we need to collect all known versions for implementation. Right now, this is done inside the .github/workflows/versioned-report.yml
workflow in a bash script (which will look pretty complicated after we add support for test harnesses outside the repository).
We could simplify this by adding a new command to bowtie
(similar to the filter-implementations
command). The new command should:
- return versions for all known test harnesses;
- provide an option to return versions for a particular test harness;
Possible ways to get the information about versions:
harnesses inside the bowtie repository
For those harnesses, we could request https://raw.githubusercontent.com/bowtie-json-schema/bowtie/refs/heads/main/implementations/<implementation name>/matrix-versions.json
. If it exists we can read it and collect all known versions.
remote harnesses
For remote harnesses, we could use GH releases API to retrieve existing releases for a test harness. If we remove v
from the tag, we should get the version for the test harness. Also, every remote harness has the latest
version.
An alternative way would be using GH packages API. We can get all the versions for a specific package (one to one mapping with test harness) and collect the versions from the labels associated with each image (it would have 2 labels with git hash and version or 3 labels - git hash, version, latest
)