ci(template): Bump actions, add scheduled integration test - #629
ci(template): Bump actions, add scheduled integration test#629Techassi wants to merge 3 commits into
Conversation
One workflow will handle the scheduled runs, the second one will handle manually dispatched ones.
| @@ -1,10 +1,7 @@ | |||
| --- | |||
| name: Integration Test | |||
| name: Integration Test (Dispatch) | |||
There was a problem hiding this comment.
As mentioned, we should split this into a profile based workflow, and a kuttl based workflow (to set specific arguments like --test and --parallel)
There was a problem hiding this comment.
You can still set --test and --test-suite with the current approach. Getting rid of interu for the dispatch would also get rid of a whole bunch of wiring (like which cluster to use, setting up env vars, etc).
There was a problem hiding this comment.
My point is the current list of inputs is kinda painful (and that's coming from me who knows how to use it).
I think others in the team will have similar complaints.
There was a problem hiding this comment.
One idea I had was a prek hook that can update a drop-down in the action so it always has selectable items. That would remove some friction.
| # At 00:00 on Sunday. See: https://crontab.guru/#0_0_*_*_0 | ||
| - cron: "0 0 * * 0" |
There was a problem hiding this comment.
I also wonder if we want to stagger these eventually. Less load on the image registry, etc...
Wish there was a random delay option in Actions.
There was a problem hiding this comment.
One idea is that we can make the schedule daily. Then each operator can have a local file with the day(s) that it should run. The workflow can bail out early if $today doesn't match the file.
There was a problem hiding this comment.
Yeah a jitter option would be nice. Also, it seems like we might want to shift the schedule slightly, because 00:00 UTC is very busy according to some threads online and results in massive delays.
There was a problem hiding this comment.
Yeah makes sense. But I think staggering tests over different days would be better.
If there are problems it gives developers some space to fix things without being overloaded at the start of the week.
Techassi
changed the title
2 participants
Caution
The
scheduleinteru profile needs to be present/commented in before the schedule will run.This PR bumps all
stackabletech/actionsactions. It also enables the integration test workflow to run on a schedule.