Open ronaldtse opened 2 weeks ago
@HassanAkbar this is so that we know what gems we can test against to know if the latest versions of lutaml-model are backwards compatible (i.e. will any user break).
@CAMOBAP a recent update of lutaml-model broke some of the gems. We wish to add an automated workflow that runs the tests of some external gems that we manage, such as:
simple ones:
complex ones:
Can we make those part of the build process (as separate jobs)? i.e. we checkout those repositories, run their specs against our local code of lutaml-model.
This will eventually include metanorma and modspec-ruby. But not until the integration issues for them are debugged and confirmed.
For now, we have two approaches for testing which are 'flavor'-based in relaton-index
and pubid-core
:
It makes sense to make a more general approach to list repo name instead flavor and reuse it in this repo + relaton-index
, pubid-core
too
Using:
In migration:
Pending migration: