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
Current scheme works fine, but there is place for improvement.
It seems that current approach of binding all the builds in the single matrix works not so good as I thought. It allows to reduce duplication, but cost is - less flexibility and ugly actions summary.
Current single matrix approach:
nlohmann/json approach:
Second is nice and clean. But has a lot of repetitions in yaml that I assume fixable with yaml's subtree substitutions.
I think it's better to mimic nlohmann/json build configurations as much as it makes sense. They have good middle ground between testing all the possible combinations of parameters and testing just a few configurations.
The text was updated successfully, but these errors were encountered:
Description
Current scheme works fine, but there is place for improvement.
It seems that current approach of binding all the builds in the single matrix works not so good as I thought. It allows to reduce duplication, but cost is - less flexibility and ugly actions summary.
Current single matrix approach:
nlohmann/json approach:
Second is nice and clean. But has a lot of repetitions in yaml that I assume fixable with yaml's subtree substitutions.
I think it's better to mimic nlohmann/json build configurations as much as it makes sense. They have good middle ground between testing all the possible combinations of parameters and testing just a few configurations.
The text was updated successfully, but these errors were encountered: