-
Notifications
You must be signed in to change notification settings - Fork 0
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
Setup GithubActions Build & Test Process #10
Comments
I think the best way to do tests will be to pull/get the Docker container (it will happen to have |
This fixes #34, and is one of the prerequisites for Nat1405/niriPipe#10.
Relevant to #10. Timed to take 9m44s for a cache miss, 7m43s for a cache hit. Hmmm...
Also relevant to #10. This approach was timed to take 1m19s. Theoretically, it has a limit of 200 pulls per 6 hours as long as authentication is working correctly. Open a new issue if you start bumping against these limits. Also, downside to this approach is that you have to trigger a new build everytime dev changes.... Buuut it might be possible to set up a GitHub Action to do that build and push for you!
All done (for now)! Closed in #6 . |
Adrian recommended switching from TravisCI to GitHub Actions for my CI process. Since it seems like a great learning opportunity, I'll try it. The requirements of this build process are:
ijiraq/gemini_processing/niri/dockerfiles/*
. This acts as a consistent environment for running data reduction code.dev
branch into the up-to-date docker container.This is a new requirement for PR #6 .
The text was updated successfully, but these errors were encountered: