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
Currently the tools we need for CI have no defined install policy. For some tools we install specific versions and make sure that version is used. For other tools we install latest or similar and sometimes check that the version we want is actually executed. I.e. for some tools the version is never actually checked.
Currently the main purpose of the versions defined in Makefile.tools is to cache tools for github actions and update the cache if necessary. This topic came up in #239.
We should agree on a policy to either pin specific version or use latest.
The text was updated successfully, but these errors were encountered:
Agree with Simon. Pinning allows reproducibility and consistency across all envs (dev, ci, ..). The additional benefit is that we cache the tools and thereby close to zero transient errors because of network issues.
Currently the tools we need for CI have no defined install policy. For some tools we install specific versions and make sure that version is used. For other tools we install
latest
or similar and sometimes check that the version we want is actually executed. I.e. for some tools the version is never actually checked.Currently the main purpose of the versions defined in
Makefile.tools
is to cache tools for github actions and update the cache if necessary. This topic came up in #239.We should agree on a policy to either pin specific version or use latest.
The text was updated successfully, but these errors were encountered: