The Frank!Runner does not always download the latest Frank!Framework version. This makes the Frank!Runner start quickly, but this behavior is not always desired for the tests. The tests may be triggered with the aim of testing the newest F!F version.
The tests can fix this by deleting frank-runner/download/metadata.
GitHub actions triggered by workflow_dispatch events can have inputs. We can force downloading the newest F!F only if this is requested through the inputs.
mhdirkse
commented
2 years ago
The Frank!Runner does not always download the latest Frank!Framework version. This makes the Frank!Runner start quickly, but this behavior is not always desired for the tests. The tests may be triggered with the aim of testing the newest F!F version.
The tests can fix this by deleting
frank-runner/download/metadata.GitHub actions triggered by workflow_dispatch events can have inputs. We can force downloading the newest F!F only if this is requested through the inputs.