-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running continunous integration tests with GPU #23
Comments
Excellent, thanks for looking into it. I agree that a custom dedicated machine is the way to go here.
Do you mean we can integrate your own server into this GitHub repository's status reporting system, using e.g. GitHub Actions? |
Yep but no need to use github actions. Just add a webhook that tell's the server when things have happened on the repo (to avoid polling). |
done but needs to be migrated to bigger server |
see #36 |
I started looking at running the tests that require GPU using hosted continuous integration tools (see alexmorley#2 (comment)) but few of them offer it and those that do are eye-wateringly expensive. I can't find it for less than $5k / month and even that won't be fully managed.
I think its really valuable to have these tests automated and reproducible ...
... so I have set up a custom Jenkins instance on an existing machine I have with a GPU. It's at jenkins.alexmorley.me and I can add anyone an account if they need it. I have it set up on my fork to run against pull requests and report the status (e.g. alexmorley#12).
Works nicely and it's pretty much free (- a bit of electricity but I can take the hit on that one 😄). At some point, I'll need @rossant to add a couple of bits of info into the Admin Settings of this repo so we can have it here too.
The text was updated successfully, but these errors were encountered: