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
We can add nightly and weekly targets the same way used for the docs, we just need to:
add if: inputs.nightly == true
add nightly to the inputs at the top of that file, default it to false.
set the targets to nightly nightly-*
We should run them after test has run, just like docs, so the long running tests fire after test has passed.
The github action can also be tuned to particular branches, as required.
We could alternatively run them instead of test by adding if: inputs.nighlty == false on the test stage.
So, we can totally tune the stages and when they run in this yaml file.
We should also add (create separate tickets for this):
in cat-voices add a time triggered github action which runs CI and sets the nightly input to true. Also add a nightly target with some example test run
nightly test report
nightly coverage report
The text was updated successfully, but these errors were encountered:
Summary
create a nightly setup
Description
We can add nightly and weekly targets the same way used for the docs, we just need to:
if: inputs.nightly == true
We should run them after test has run, just like docs, so the long running tests fire after test has passed.
The github action can also be tuned to particular branches, as required.
We could alternatively run them instead of test by adding if: inputs.nighlty == false on the test stage.
So, we can totally tune the stages and when they run in this yaml file.
We should also add (create separate tickets for this):
The text was updated successfully, but these errors were encountered: