The travis-new.yml holds a new Travis configuration approach we want to switch to. It should test the subproject in their individual languages etc. For now, we only test the API and the Engine since both is based on Scala and SBT. The matrix approach should test Beta in Elm too.
Although the Elm config works for Beta, the API and Engine fail due to a not further specified issue of Travis. Yet the config approach is frequently given on the web.
travis lint on the file reports several issues, which makes me believe that this is a more recent change that broke the compatibility.
mpgirro
commented
5 years ago
The travis-new.yml holds a new Travis configuration approach we want to switch to. It should test the subproject in their individual languages etc. For now, we only test the API and the Engine since both is based on Scala and SBT. The matrix approach should test Beta in Elm too.
Although the Elm config works for Beta, the API and Engine fail due to a not further specified issue of Travis. Yet the config approach is frequently given on the web.
travis linton the file reports several issues, which makes me believe that this is a more recent change that broke the compatibility.