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
It should be possible to add Gitlab CI with a few test cases to this tool itself so that we can ensure it still does its job when updating it without manual involvement and while not making our entire Ginkgo pipelines fail during testing.
To do so, we would need to register a test/beta runner on an HPC machine. A problem is that for now, BwUni seems to only support one runner per user (from previous tests)?
Managing the runner's script update on the server-side might be a bit more tricky without relying on ssh, maybe a simple cron job would be sufficient with a trigger from the server-side when master is updated.
The text was updated successfully, but these errors were encountered:
It should be possible to add Gitlab CI with a few test cases to this tool itself so that we can ensure it still does its job when updating it without manual involvement and while not making our entire Ginkgo pipelines fail during testing.
To do so, we would need to register a test/beta runner on an HPC machine. A problem is that for now, BwUni seems to only support one runner per user (from previous tests)?
Managing the runner's script update on the server-side might be a bit more tricky without relying on
ssh
, maybe a simplecron
job would be sufficient with a trigger from the server-side whenmaster
is updated.The text was updated successfully, but these errors were encountered: